An Accepted Solution is available for this post.
Chino Hills...AGAIN
Hairstylinstacy
Enthusiast - Level 1
‎11-02-2009 04:52 PM

Well looks like it's back again(at least on my end). Nothing has changed on my end, was good for awhile, but starting around 4pm today it's getting out of hand again.

Tracing route to verizon.com [192.76.85.245]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2   239 ms   433 ms   287 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3    31 ms     6 ms     9 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4   249 ms   158 ms   134 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5   256 ms   363 ms   342 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6   357 ms   295 ms   307 ms  0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
  7   334 ms   320 ms   318 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
  8   170 ms   187 ms   176 ms  verizon-gw.customer.alter.net [157.130.203.246]

  9   296 ms   241 ms   266 ms  192.76.84.5
 10     *        *        *     Request timed out.

0 Likes
Reply
45 Replies
An Accepted Solution is available for this post.
chinorider
Enthusiast - Level 3
In response to Osler
‎11-06-2009 07:40 AM

I am also in Chino Hills and have recently noticed the VERY poor internet speeds.  I am glad it isn't just me.  I will try some of the trace routes when I get home from work today.  Speed tests show less than 1Mbps up or down !!!!

What number should I call to report the problem.  Maybe the more reports Vz gets they will begin to realize this is a system problem and not a bunch of bad routers....

Thanks

0 Likes
Reply
An Accepted Solution is available for this post.
dwoo
Enthusiast - Level 2
‎11-06-2009 11:03 AM

11:00am 11/6/2009 @ Chino Hills

C:\>tracert verizon.net

Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:

  1     6 ms     2 ms     2 ms  L101.VFTTP-142.LSANCA.verizon-gni.net [71.254.182.1]
  2     6 ms     4 ms     4 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  3     7 ms     8 ms     6 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  4    44 ms    42 ms    42 ms  so-7-3-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.125]
  5    44 ms    44 ms    43 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  6    45 ms    43 ms    43 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  7    45 ms    45 ms    44 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
  8    43 ms    42 ms    43 ms  206.46.228.131
  9    47 ms    46 ms    44 ms  206.46.232.39

Trace complete.

Thank you Brett

0 Likes
Reply
An Accepted Solution is available for this post.
Torched
Enthusiast - Level 2
‎11-06-2009 11:40 AM

11:30 AM Chino Hills, Ca seems OK now but it has always been good in the morning and gets much worse at night.

Tracing route to e3002.b.akamaiedge.net [72.247.92.79]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     9 ms     8 ms     6 ms  l100.lsanca-vfttp-142.verizon-gni.net [173.55.53.1]
  3    13 ms    12 ms    12 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4    12 ms    12 ms    12 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27.31]
  5    15 ms    14 ms    15 ms  so-4-3-0-0.lax01-bb-rtr2.verizon-gni.net [130.81.29.246]
  6    14 ms    14 ms    14 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  7    15 ms    15 ms    14 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]

  8    15 ms    14 ms    14 ms  ge8-3-10G.ar4.LAX2.gblx.net [64.212.107.121]
  9    12 ms    11 ms    13 ms  te2-3-10G.ar4.LAX1.gblx.net [67.17.107.42]
 10    15 ms    14 ms    12 ms  a72-247-92-79.deploy.akamaitechnologies.com [72.247.92.79]

Trace complete.

I'll post more later today/tonight.

0 Likes
Reply
An Accepted Solution is available for this post.
VZ_Brett
Contributor - Level 2
In response to Torched
‎11-06-2009 11:57 AM

Keep an eye on it tonight, and post traceroutes back. I will keep following up with it. Thanks Brett

0 Likes
Reply
An Accepted Solution is available for this post.
chinorider
Enthusiast - Level 3
‎11-06-2009 04:00 PM

Tried trace route at 4 pm - local.  All good

tracert www.verizon.net

Tracing route to e3002.b.akamaiedge.net [72.247.92.79]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     7 ms     7 ms    11 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
  3    12 ms     9 ms     9 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4     8 ms    10 ms     9 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  5    11 ms    12 ms    12 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
  6    12 ms    15 ms    11 ms  0.ge-7-0-0.BR2.LAX15.ALTER.NET [152.63.116.157]
  7    15 ms    12 ms    12 ms  ge8-3-10G.ar4.LAX2.gblx.net [64.212.107.121]
  8    13 ms    12 ms    12 ms  te2-3-10G.ar4.LAX1.gblx.net [67.17.107.42]
  9    12 ms    12 ms    11 ms  a72-247-92-79.deploy.akamaitechnologies.com [72.247.92.79]

Trace complete.

0 Likes
Reply
An Accepted Solution is available for this post.
Hairstylinstacy
Enthusiast - Level 1
In response to chinorider
‎11-06-2009 05:37 PM

5:30pm everything looking good again.

Tracing route to verizon.com [192.76.85.245]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     4 ms     4 ms     5 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3     8 ms     7 ms     7 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4     8 ms     8 ms     9 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5     9 ms     7 ms     8 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6    21 ms    21 ms    21 ms  0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
  7    23 ms    23 ms    24 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
  8    24 ms    24 ms    25 ms  verizon-gw.customer.alter.net [157.130.203.246]

  9    25 ms    24 ms    25 ms  192.76.84.5
 10     *        *        *     Request timed out.

0 Likes
Reply
An Accepted Solution is available for this post.
chinorider
Enthusiast - Level 3
In response to Hairstylinstacy
‎11-06-2009 06:35 PM

You have a time out...that is not good....

0 Likes
Reply
An Accepted Solution is available for this post.
nestacio
Enthusiast - Level 2
In response to chinorider
‎11-06-2009 06:56 PM

Brett, it's looking pretty good as of 7pm PST tonight:

Tracing route to www.l.google.com [74.125.19.106]

over a maximum of 30 hops:


  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]

  2     7 ms     6 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]

  3    10 ms    10 ms     9 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]

  4    10 ms     8 ms    10 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]

  5    10 ms     9 ms    10 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]

  6    13 ms    12 ms    12 ms  0.ge-7-0-0.BR2.LAX15.ALTER.NET [152.63.116.157]

  7    12 ms    41 ms    12 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]

  8    11 ms    19 ms    19 ms  ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]

  9    23 ms    34 ms    34 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]

 10    32 ms    34 ms    36 ms  ae-93-93.csw4.SanJose1.Level3.net [4.69.134.238]

 11    20 ms    21 ms    22 ms  ae-4-99.edge1.SanJose1.Level3.net [4.68.18.206]

 12    25 ms    21 ms    25 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]

 13    23 ms    32 ms    34 ms  209.85.251.98

 14    18 ms    19 ms    22 ms  nuq04s01-in-f106.1e100.net [74.125.19.106]


Trace complete.

Anyone else seeing decent numbers? Nice work again, glad Verizon has guys like you making sure things are running smooth.

Neil

0 Likes
Reply
An Accepted Solution is available for this post.
jco88
Newbie
‎11-06-2009 08:02 PM

Looking good still... since it's not going thru the troubled LSANCA-LCR-12 router (ipaddress 130.81.140.162) , we're good....

it's only when we go that route that the problem occurs... 

Target Name: www.verizon.net

         IP: 72.247.92.79

  Date/Time: 11/6/2009 7:59:23 PM

 1    3 ms  Wireless_Broadband_Router.home [192.168.1.1]

 2    5 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]

 3   11 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]

 4   11 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27.31]

 5   14 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]

 6   13 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]

 7   15 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]

 8   13 ms  ge8-3-10G.ar4.LAX2.gblx.net [64.212.107.121]

 9   16 ms  te2-3-10G.ar4.LAX1.gblx.net [67.17.107.42]

10   13 ms  a72-247-92-79.deploy.akamaitechnologies.com [72.247.92.79]

Ping statistics for www.verizon.net

Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)

Round Trip Times: Minimum = 13ms, Maximum = 13ms, Average = 13ms

0 Likes
Reply
An Accepted Solution is available for this post.
MisterJefferson
Enthusiast - Level 3
‎11-06-2009 08:42 PM

Hooray! Things look better again.

11/6/09, 8:40pm:

Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     7 ms     8 ms     6 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3    11 ms    13 ms    11 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4    11 ms    12 ms    12 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27.31]
  5    15 ms    14 ms    29 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  6    50 ms    50 ms    49 ms  130.81.17.27
  7    50 ms    48 ms    49 ms  ge-3-1-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.68]
  8    48 ms    50 ms    49 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  9    49 ms    51 ms    48 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
 10    52 ms    49 ms    50 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 11    50 ms    49 ms    50 ms  206.46.228.130
 12    49 ms    49 ms    50 ms  206.46.232.39

Trace complete.

0 Likes
Reply
An Accepted Solution is available for this post.
VZ_Brett
Contributor - Level 2
In response to MisterJefferson
‎11-07-2009 07:52 AM

Good deal so far!! Dont close the thread down yet. If you guys could please keep any eye on it for the next couple of days & keep posting so I can follow! Thank you all for your help! Brett

0 Likes
Reply
An Accepted Solution is available for this post.
chinorider
Enthusiast - Level 3
‎11-07-2009 09:24 AM


tracert www.verizon.net

Tracing route to e3002.b.akamaiedge.net [69.192.44.79]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     8 ms     7 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
  3     8 ms    10 ms     9 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4     9 ms    12 ms     9 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  5    13 ms    12 ms     9 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6    10 ms    10 ms    12 ms  POS6-0.BR2.LAX7.ALTER.NET [152.63.112.145]
  7     9 ms     9 ms    10 ms  p64-5-0-1.r20.lsanca03.us.bb.gin.ntt.net [129.250.8.69]
  8    12 ms    10 ms     9 ms  po-1.r00.lsanca03.us.bb.gin.ntt.net [129.250.5.254]
  9    11 ms    13 ms    11 ms  a69-192-44-79.deploy.akamaitechnologies.com [69.192.44.79]

Trace complete.

Still OK at 9:25 am

0 Likes
Reply
An Accepted Solution is available for this post.
MisterJefferson
Enthusiast - Level 3
‎11-07-2009 06:00 PM

Still looks good.  11/7/09, 5:54pm:

Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2    38 ms    29 ms    30 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3    12 ms    11 ms    12 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4    11 ms    12 ms    12 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27.31]
  5    14 ms    14 ms    14 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  6    49 ms    49 ms    50 ms  130.81.17.27
  7    49 ms    49 ms    50 ms  ge-3-1-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.68]
  8    49 ms    49 ms    50 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  9    56 ms    50 ms    49 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
 10    49 ms    50 ms    49 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 11    48 ms    50 ms    49 ms  206.46.228.130
 12    48 ms    50 ms    49 ms  206.46.232.39

Trace complete.


Speakeasy (Los Angeles):  19751/4339

Speakeasy (Dallas): 19777/4564

Speakeasy (New York): 12342/1043

Speedtest.net (Los Angeles): 19.76M/4.58M; 10ms ping

Speedtest.net (Dallas): 19.78M/4.36M; 50ms ping

Speedtest.net (DC): 19.83M/2.57M; 84ms ping

0 Likes
Reply
An Accepted Solution is available for this post.
VZ_Brett
Contributor - Level 2
In response to MisterJefferson
‎11-09-2009 10:36 AM

Hello All , anybody still seeing any latency issue w/ LSANCA-LCR-12. Let me know thanks Brett

0 Likes
Reply
An Accepted Solution is available for this post.
chinorider
Enthusiast - Level 3
In response to VZ_Brett
‎11-09-2009 02:22 PM
@VZ_Brett wrote:

Hello All , anybody still seeing any latency issue w/ LSANCA-LCR-12. Let me know thanks Brett

I do not see LSANCA-LCR-12 in any tracert I have run over the week-end. It looks like -12 is out of the route.  All seems fine for now.

Thanks

0 Likes
Reply
An Accepted Solution is available for this post.
MisterJefferson
Enthusiast - Level 3
In response to VZ_Brett
‎11-09-2009 10:06 PM

Looks okay tonight.  11/9/09, 10:01pm.

Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     7 ms     6 ms     8 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3     7 ms     7 ms     7 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4     8 ms    10 ms     9 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5    59 ms    43 ms    45 ms  130.81.17.27
  6    45 ms    46 ms    47 ms  ge-3-1-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.68]
  7    46 ms    47 ms    47 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  8    46 ms    47 ms    47 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  9    48 ms    47 ms    47 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 10    45 ms    47 ms    47 ms  206.46.228.130
 11    46 ms    47 ms    47 ms  206.46.232.39

Trace complete.

0 Likes
Reply
An Accepted Solution is available for this post.
jco88
Newbie
‎11-09-2009 11:43 PM

this is really weird. i'm get this nice trace route output but i'm unable to go to different websites tonight.   even verizon.net is not coming up or is taking a long time. facebook.com, hulu.com, youtube.com all give me problems. i rebooted the router a few times and even reset. i called tech support, they had me bypass the router and directly plug to my wall outlet. they reset my dhcp lease, and i still get the same weird problem. but every traceroute give me what you see below.  any ideas?

$ tracert verizon.net

Tracing route to verizon.net [206.46.232.39]

over a maximum of 30 hops:

  1     4 ms     2 ms     2 ms  Wireless_Broadband_Router.home [192.168.1.1]

  2     7 ms     7 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]

  3     7 ms     7 ms     7 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]

  4    10 ms     9 ms     9 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]

  5    45 ms    44 ms    44 ms  130.81.17.27

  6    44 ms    44 ms    44 ms  so-7-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.12]

  7    46 ms    47 ms    47 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]

  8    45 ms    47 ms    47 ms  po1.ctn-border1.vzlink.com [206.46.225.85]

  9    46 ms    47 ms    54 ms  po121.ctn-core1.vzlink.com [206.46.225.18]

 10    49 ms    47 ms    47 ms  206.46.228.130

 11    47 ms    47 ms    47 ms  206.46.232.39

Trace complete.

0 Likes
Reply
An Accepted Solution is available for this post.
dwoo
Enthusiast - Level 2
‎11-10-2009 12:52 AM

I have same issue

"Can't display few websites" (instead of can't CONNECT to some websites)

for example,

when i connect to www.msn.com, browser keeps loading and loading and nothing comes in, I clicked stop and went to view "source", it displayed fine, but for some reason browser won't display it correctly.

here is the list i found out not working fine tonight:

facebook.com

msn.com

verizon.net

newegg.com

www.w3.org

Above won't load the first page

and for other website, first page loaded but still running feel like something still downloading and takes forever to finish.

espn.com

below is good site list

www.google.com

www.yahoo.com

I will do some research tomorrow 

0 Likes
Reply
An Accepted Solution is available for this post.
jco88
Newbie
‎11-10-2009 09:07 AM

i thought it was just me,  my officemate who also lives in Chino Hills is experiencing the same problem i have. A lot of sites we're able to reach but can't get the page to load. It just sits on 'loading' forever. the only one that works consistenly is www.google.com.  I ran some test using a unix utility called 'wget'. i did 'wget  <site url>' to a number of sites.  I'm able to connect to the site but i'm not able to a HTTP 200 OK response most of the time but to google.com, it's always the 200 OK  status. Somewhere in the verizon network, the response is not coming back correctly, could it be a router issue?  We've seen similar behavior in the company i work for and it was a router.  

The other odd thing is this morning, things seem to be fine. It's one of those things that happen in the evenings only. I'm really getting tired of this problem. Can i even get billing credit from verizon for 1 month of trouble now?

i'll try again tonight and post my trace..

0 Likes
Reply
An Accepted Solution is available for this post.
VZ_Brett
Contributor - Level 2
In response to jco88
‎11-10-2009 09:15 AM

can you guys post some traceroutes to some of the sites you cant get to, Thanks.

0 Likes
Reply
An Accepted Solution is available for this post.
jco88
Newbie
‎11-10-2009 09:54 AM

sure Bret, will post traces tonight. thanks.

0 Likes
Reply