An Accepted Solution is available for this post. Jump to solution.
High latency and poor speed tests lately
MisterJefferson
Enthusiast - Level 3
‎10-20-2009 08:24 PM

For the past 4-5 days, I've been working with various Verizon techs to resolve a high latency/slow Internet problem.  Their ultimate solution was that they have no idea why it's doing this, and since I can reach a few websites at full speed and their line tests show I'm operating at full provisioning, it's not their problem.  "We can't control traffic outside of our networks."  Well, my results are also showing problems with the Verizon servers, so I would think they should be more concerned.  Most websites, however, exhibit the problem.  So I'm stuck, looking for a better answer than "go away."  Maybe some of you are experiencing a similar problem with latency or sporadic speeds?

My provisioning is 20M/5M.  I'm in the L.A. area. (In the traceroutes below, I masked Hop 2 for privacy.)

I've experienced this problem with 2 computers (1 desktop, 1 laptop), both using Ethernet ports; one test using wireless on the laptop.  I've plugged the router directly into the ONT coax to eliminate my house wiring as the culprit.  Westell 9100EM router.

A few websites seem okay, and speedtest.net results always show provisioning at full speed to the L.A. server, but the problem persists when using the non-L.A. server.  With speakeasy.net, even the L.A. server exhibits the problem.  The latency gets worse as the night goes on, sometimes over 1000ms for some traceroute hops.  In the morning, it seems to be back to normal.

Thanks for any help....

Jeff

Some examples...

In the past 2 mornings, I've had good results:

Speed Test (speakeasy.net, Los Angeles): ~ 19798K/4581K

Speed Test (speedtest.net, Los Angeles): always shows full provisioning ~19.74M, 4.56M, 19ms ping

Speed Test (speedtest.net, Dallas): ~ 19.81M/4.37M, 49ms ping

Tracing route to www.l.google.com [74.125.19.104]
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  xxxx.xxxxx-xxxxx-xxxxx.verizon-gni.net [173.55.xxx.xxx]
  3     8 ms    10 ms     9 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4    11 ms    53 ms    11 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  5    13 ms    12 ms    12 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
  6    12 ms    11 ms    13 ms  0.ge-7-0-0.BR2.LAX15.ALTER.NET [152.63.116.157]
  7     9 ms    12 ms    42 ms  xe-11-0-0.edge1.SanJose3.level3.net [4.68.111.249]
  8    14 ms    12 ms    17 ms  ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.52]
  9    21 ms    34 ms    35 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10    26 ms    19 ms    19 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
 11    21 ms    22 ms    22 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
 12    23 ms    22 ms    23 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 13    29 ms    34 ms    22 ms  209.85.251.98
 14    20 ms    23 ms    19 ms  nuq04s01-in-f104.1e100.net [74.125.19.104]

In the past 4-5 evenings, I've had poor results:

Speed Test (speakeasy.net, Los Angeles): ~ 2441K/194K

Speed Test (speedtest.net, Los Angeles): always shows full provisioning ~19.74M, 4.56M, 19ms ping

Speed Test (speedtest.net, Dallas): ~ 8.28M/1.22M, 49ms ping

Tracing route to www.l.google.com [74.125.19.105]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     7 ms     7 ms     7 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3   531 ms   502 ms   514 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   519 ms   506 ms   530 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   563 ms   564 ms   553 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6   577 ms   544 ms   524 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
  7   477 ms   469 ms   459 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  8    11 ms    17 ms    19 ms  ae-93-90.ebr3.LosAngeles1.Level3.net [4.69.144.244]
  9   515 ms   559 ms   536 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10    20 ms    19 ms    19 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
 11   524 ms   499 ms   544 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
 12   490 ms   479 ms   464 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 13    24 ms    22 ms    32 ms  209.85.251.98
 14    23 ms    22 ms   489 ms  nuq04s01-in-f105.1e100.net [74.125.19.105]

0 Likes
Reply
1 Solution
An Accepted Solution is available for this post. Jump to solution.
MisterJefferson
Enthusiast - Level 3
‎10-30-2009 12:44 AM

It looks fixed on my end, so I hope this is a permanent thing.  My speed tests are back to normal, and I'm seeing much more reasonable latency.  Thanks, Brett, for following up.

- Jeff

Taken tonight, 10/30, 12:30am:

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     7 ms     7 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3    12 ms    12 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    12 ms    12 ms    12 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  6    49 ms    77 ms    64 ms  130.81.17.27
  7    49 ms    50 ms    49 ms  so-1-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.66]
  8    50 ms    50 ms    49 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  9    49 ms    50 ms    49 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
 10    51 ms    49 ms    54 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 11    48 ms    49 ms    50 ms  206.46.228.130
 12    49 ms    50 ms    49 ms  206.46.232.39

Trace complete.

Taken tonight, 10/30, 12:40am:

Tracing route to www.l.google.com [74.125.19.104]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     7 ms     7 ms     7 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3     9 ms     9 ms    10 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    12 ms     9 ms    10 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
  6     8 ms    12 ms    10 ms  0.ge-6-0-0.BR2.LAX15.ALTER.NET [152.63.116.149]
  7    12 ms    12 ms    12 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  8    13 ms    14 ms    17 ms  ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.52]
  9    33 ms    34 ms    34 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10    32 ms    17 ms    19 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
 11    20 ms    22 ms    23 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
 12    19 ms    19 ms    19 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 13    29 ms    22 ms    32 ms  209.85.251.98
 14    18 ms    19 ms    19 ms  nuq04s01-in-f104.1e100.net [74.125.19.104]

Trace complete.

View solution in original post

0 Likes
Reply
127 Replies
An Accepted Solution is available for this post. Jump to solution.
jco88
Newbie
‎10-28-2009 10:04 PM

from chino hills again... getting slower as the night goes on...

Target Name: www.hulu.com
         IP: 65.200.11.147
  Date/Time: 10/28/2009 9:58:04 PM

 1    0 ms  Wireless_Broadband_Router.home [192.168.1.1]
 2    3 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
 3  555 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
 4  554 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
 5  553 ms  0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
 6  556 ms  0.so-7-1-0.XL4.LAX15.ALTER.NET [152.63.1.242]
 7   16 ms  TenGigE0-7-1-0.GW4.LAX15.ALTER.NET [152.63.114.225]
 8  564 ms  a65.200.11.147.deploy.akamaitechnologies.com [65.200.11.147]

Ping statistics for www.hulu.com
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 564ms, Maximum = 564ms, Average = 564ms

Target Name: www.google.com
         IP: 74.125.19.103
  Date/Time: 10/28/2009 10:03:27 PM

 1    0 ms  Wireless_Broadband_Router.home [192.168.1.1]
 2    3 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
 3  527 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
 4  534 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
 5  544 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
 6   16 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
 7  551 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
 8   25 ms  ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.52]
 9   28 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10  551 ms  ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]
11   14 ms  ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]
12   12 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
13   18 ms  [209.85.251.98]
14  558 ms  nuq04s01-in-f103.1e100.net [74.125.19.103]

Ping statistics for www.google.com
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 558ms, Maximum = 558ms, Average = 558ms

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
jco88
Newbie
‎10-28-2009 10:22 PM

used to be able to watch apple.com HD trailers with no problems.. these days, i have to let it download first or else, it's constantly pausing. it's like having DSL connection but paying FIOS rates.. this is not right at all...  it's been 2 weeks now.

Target Name: apple.com
         IP: 17.112.152.57
  Date/Time: 10/28/2009 10:19:44 PM

 1    0 ms  Wireless_Broadband_Router.home [192.168.1.1]
 2    2 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
 3  509 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
 4  509 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
 5  509 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
 6    4 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
 7    5 ms  [192.205.35.161]
 8   15 ms  cr1.la2ca.ip.att.net [12.123.30.6]
 9   14 ms  cr1.sffca.ip.att.net [12.122.3.121]
10  517 ms  cr1.sc1ca.ip.att.net [12.122.30.121]
11   13 ms  gar2.sc1ca.ip.att.net [12.123.155.9]
12   15 ms  [12.116.180.6]
13   17 ms  [17.112.254.24]
14   14 ms  [17.112.254.29]
15  522 ms  apple.com [17.112.152.57]

Ping statistics for apple.com
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 522ms, Maximum = 522ms, Average = 522ms

Target Name: www.verizon.com
         IP: 65.200.11.147
  Date/Time: 10/28/2009 10:20:23 PM

 1    0 ms  Wireless_Broadband_Router.home [192.168.1.1]
 2   12 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
 3  514 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
 4  513 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
 5  511 ms  0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
 6  521 ms  0.so-7-1-0.XL4.LAX15.ALTER.NET [152.63.1.242]
 7    8 ms  TenGigE0-7-1-0.GW4.LAX15.ALTER.NET [152.63.114.225]
 8  525 ms  a65.200.11.147.deploy.akamaitechnologies.com [65.200.11.147]

Ping statistics for www.verizon.com
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 525ms, Maximum = 525ms, Average = 525ms

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
Customer1125
Newbie
In response to jco88
‎10-28-2009 11:38 PM

I'm getting poor results as well. Thought it was just me. Used pingtest.net. Tech support told us we just have an old computer. Never had this problem when I had cable from Time Warner.

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
Richard312
Newbie
In response to Customer1125
‎10-29-2009 12:01 AM

Nope not fixed

Taken exactly at midnight


Tracing route to www.l.google.com [74.125.19.99]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  myrouter.home [192.168.1.1]
  2     5 ms     5 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3   505 ms   511 ms   507 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   515 ms   544 ms   521 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   567 ms   594 ms   593 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6     8 ms     9 ms     8 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

  7   576 ms   579 ms   569 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  8    10 ms    17 ms    17 ms  ae-93-90.ebr3.LosAngeles1.Level3.net [4.69.144.244]
  9    16 ms    17 ms    17 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10   631 ms   626 ms   573 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]

 11   643 ms   668 ms   640 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]

 12   675 ms   681 ms   703 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 13   678 ms   631 ms   622 ms  209.85.251.98
 14   549 ms   517 ms   558 ms  nuq04s01-in-f99.1e100.net [74.125.19.99]

Trace complete.

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
VZ_Brett
Contributor - Level 2
In response to Richard312
‎10-29-2009 07:18 AM

Thanks everyone, I just let them know & waiting on a response! Brett

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
dwoo
Enthusiast - Level 2
‎10-29-2009 12:00 AM

12:00am, latest tracert to google.com

Tracing route to google.com [74.125.45.100]
over a maximum of 30 hops:

  1     4 ms     6 ms    15 ms  L300.LSANCA-VFTTP-142.verizon-gni.net [private]
  2   667 ms   614 ms   613 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  3   636 ms   614 ms   613 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  4   636 ms   499 ms   523 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  5   546 ms   511 ms   614 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
  6     7 ms     6 ms     5 ms  192.205.35.161
  7    62 ms    61 ms    66 ms  cr2.la2ca.ip.att.net [12.123.30.134]
  8    63 ms    61 ms    61 ms  cr2.dlstx.ip.att.net [12.122.28.177]
  9   665 ms   716 ms   716 ms  cr1.attga.ip.att.net [12.122.28.173]
 10   666 ms   716 ms   717 ms  12.123.22.5
 11   842 ms   707 ms   714 ms  12.88.97.6
 12   635 ms   613 ms   614 ms  72.14.233.54
 13    63 ms    75 ms   189 ms  72.14.232.213
 14    68 ms   655 ms   716 ms  209.85.253.145
 15   684 ms   761 ms   674 ms  yx-in-f100.1e100.net [74.125.45.100]

Trace complete.

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
Hairstylinstacy
Enthusiast - Level 1
‎10-29-2009 08:45 AM
Thanks for keeping us updated.
0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
VZ_Brett
Contributor - Level 2
In response to Hairstylinstacy
‎10-29-2009 10:22 AM

All, they are asking to re-test now. I did advised that it mostly is in the evening into the night so once you all have a chance start posting trace routes. Thanks AGAIN!! 

Reply
An Accepted Solution is available for this post. Jump to solution.
Hairstylinstacy
Enthusiast - Level 1
In response to VZ_Brett
‎10-29-2009 10:31 AM

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     5 ms     6 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3     7 ms     6 ms     7 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4     6 ms     7 ms     7 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  5     6 ms    11 ms     7 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
  6    22 ms    20 ms    22 ms  0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
  7    26 ms    23 ms    33 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
  8    21 ms    20 ms    21 ms  verizon-gw.customer.alter.net [157.130.203.246]

  9    24 ms    29 ms    33 ms  192.76.84.5

10 + Timed Out

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
dwoo
Enthusiast - Level 2
‎10-29-2009 10:45 AM

Wow, looks good this morning (as 10:40am 10-29-2009), hopefully this evening stay the same.

Tracing route to google.com [74.125.45.100]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  L101.VFTTP-142.LSANCA.verizon-gni.net [private]
  2     4 ms     5 ms     3 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  3    11 ms    11 ms     8 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  4     8 ms     5 ms     6 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  5     7 ms     6 ms     7 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
  6     7 ms     4 ms     6 ms  192.205.35.161
  7    62 ms    60 ms    61 ms  cr2.la2ca.ip.att.net [12.123.30.134]
  8    65 ms    61 ms    60 ms  cr2.dlstx.ip.att.net [12.122.28.177]
  9   167 ms   110 ms    86 ms  cr1.attga.ip.att.net [12.122.28.173]
 10   115 ms   131 ms    75 ms  12.123.22.5
 11    81 ms    83 ms    80 ms  12.88.97.6
 12   309 ms    98 ms    83 ms  72.14.233.54
 13    61 ms    78 ms    68 ms  72.14.232.215
 14    69 ms    69 ms    72 ms  209.85.253.145
 15    87 ms    89 ms    83 ms  yx-in-f100.1e100.net [74.125.45.100]

Trace complete.

Tracing route to verizone.com [64.124.14.63]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  L101.VFTTP-142.LSANCA.verizon-gni.net [private]
  2     4 ms     3 ms     4 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  3     4 ms     4 ms     4 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  4     7 ms     4 ms     4 ms  0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
  5     8 ms     6 ms     7 ms  0.ge-7-0-0.BR2.LAX15.ALTER.NET [152.63.116.157]
  6    10 ms     6 ms     5 ms  so-0-1-3.mpr4.lax9.us.above.net [64.125.13.53]
  7    16 ms    13 ms    14 ms  so-0-1-0.mpr2.sjc2.us.above.net [64.125.26.30]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10    59 ms    45 ms    51 ms  forward.markmonitor.com [64.124.14.63]

Trace complete.

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
VZ_Brett
Contributor - Level 2
In response to dwoo
‎10-29-2009 10:47 AM

Yes we are all keeping our fingers crossed!!

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
Hairstylinstacy
Enthusiast - Level 1
‎10-29-2009 01:25 PM

1:00pm

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

  9    35 ms    23 ms    25 ms  192.76.84.5
 10     *        *        *     Request timed out.

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
dwoo
Enthusiast - Level 2
‎10-29-2009 03:50 PM

3:50pm

Tracing route to google.com [74.125.67.100]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  L101.VFTTP-142.LSANCA.verizon-gni.net [not private, hide for fun]
  2     8 ms     7 ms     6 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  3     8 ms     6 ms     6 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27.31]
  4     9 ms     8 ms     9 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5    11 ms     9 ms    10 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6     9 ms     7 ms     8 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
  7     8 ms     6 ms     6 ms  192.205.35.161
  8    65 ms    62 ms    63 ms  cr2.la2ca.ip.att.net [12.123.30.134]
  9    65 ms    63 ms    64 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 10    71 ms    69 ms    69 ms  cr1.attga.ip.att.net [12.122.28.173]
 11    69 ms   132 ms    69 ms  12.123.22.5
 12    71 ms    71 ms    69 ms  12.88.97.6
 13    65 ms    62 ms    64 ms  72.14.233.56
 14    72 ms    69 ms    65 ms  209.85.254.247
 15    69 ms    74 ms    71 ms  209.85.255.198
 16    72 ms    71 ms    71 ms  gw-in-f100.1e100.net [74.125.67.100]

Trace complete.

eh? what happened to LSANCA-LCR-12 ? you guys unpluged it ?? 😄

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
Torched
Enthusiast - Level 2
‎10-29-2009 04:04 PM

Looking good so far but its still early: Chino Hills, Ca 4:00 PM

Interesting how I'm going through both LCR-11 & LCR-12 now, thats different then before.

Tracing route to www.l.google.com [66.102.7.105]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 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    14 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    13 ms    12 ms    12 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  6    14 ms    14 ms    15 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  7    12 ms    12 ms    22 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

  8    12 ms    12 ms    12 ms  192.205.35.161
  9    28 ms    27 ms    27 ms  cr1.la2ca.ip.att.net [12.123.30.6]
 10    30 ms    29 ms    30 ms  cr1.sffca.ip.att.net [12.122.3.121]
 11    27 ms    27 ms    27 ms  12.122.114.45
 12    26 ms    27 ms    27 ms  12.88.147.10
 13   102 ms    25 ms    24 ms  72.14.239.250
 14    37 ms    37 ms    37 ms  216.239.43.145
 15    45 ms    39 ms    49 ms  72.14.239.246
 16    35 ms    32 ms    34 ms  lax04s01-in-f105.1e100.net [66.102.7.105]

Trace complete.

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

  1    <1 ms    <1 ms    <1 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    12 ms    11 ms    13 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4    12 ms    13 ms    11 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27.31]
  5    11 ms    12 ms    12 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  6    18 ms    14 ms    15 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  7    13 ms    12 ms    12 ms  0.so-7-3-0.XT2.LAX7.ALTER.NET [152.63.112.62]
  8    12 ms    13 ms    14 ms  0.so-7-0-0.BR1.LAX7.ALTER.NET [152.63.112.153]
  9    11 ms    14 ms    13 ms  204.255.168.34
 10    14 ms    14 ms    12 ms  los-core-02.inet.qwest.net [205.171.32.13]
 11    13 ms    13 ms    11 ms  los-edge-01.inet.qwest.net [205.171.32.46]
 12    12 ms    11 ms    12 ms  a96-6-60-79.deploy.akamaitechnologies.com [96.6.60.79]

Trace complete.

Crossing my fingers and hoping for the best, i'll post more results later this evening.

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
Napa21
Newbie
‎10-29-2009 04:50 PM

A couple of things you can do is do download this http://onecare.live.com/site/en-us/center/cleanup.htm it free from microsoft and it will cleanup all your junk and also go to System Configuration and see what services are running and disable anything you don`t need.

                                    Napa21

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
Hairstylinstacy
Enthusiast - Level 1
‎10-29-2009 05:44 PM

Everything is looking great here! Hopefully everyone has similiar results and we can close this thread down.

Taken at 5:30pm

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

  9    23 ms    23 ms    25 ms  192.76.84.5

10+ Timed out

Tracing route to worldofwarcraft.com [12.129.242.22]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     3 ms     4 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3     9 ms     8 ms     9 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4     9 ms     8 ms     9 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27
.31]
  5    10 ms    10 ms    12 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
  6    11 ms    12 ms    13 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  7    10 ms     9 ms    10 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

  8    12 ms    13 ms    12 ms  192.205.35.161
  9    10 ms     9 ms    13 ms  cr2.la2ca.ip.att.net [12.123.30.134]
 10    12 ms    12 ms    13 ms  gar4.la2ca.ip.att.net [12.122.129.169]
 11   125 ms   199 ms   203 ms  12.122.255.70
 12    14 ms    12 ms    12 ms  12.129.193.254
 13 +    *        *        *     Request timed out.

Tracing route to google.com [74.125.45.100]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     4 ms     5 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3     9 ms     7 ms     8 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  4    10 ms     9 ms    10 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27
.31]
  5    11 ms    12 ms    10 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
  6     *       12 ms    12 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  7    12 ms    11 ms    12 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]

  8    11 ms    12 ms    12 ms  192.205.35.161
  9    66 ms    64 ms    65 ms  cr2.la2ca.ip.att.net [12.123.30.134]
 10    65 ms    67 ms    66 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 11    67 ms    65 ms    65 ms  cr1.attga.ip.att.net [12.122.28.173]
 12    65 ms    65 ms    64 ms  12.123.22.5
 13    71 ms    71 ms    71 ms  12.88.97.6
 14    82 ms    64 ms    67 ms  72.14.233.56
 15    65 ms    65 ms    65 ms  209.85.254.243
 16    70 ms    71 ms    71 ms  209.85.253.137
 17    74 ms    73 ms    71 ms  yx-in-f100.1e100.net [74.125.45.100]

Trace complete.

Thanks again Brett for all your help.

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
MisterJefferson
Enthusiast - Level 3
In response to Hairstylinstacy
‎10-30-2009 09:21 PM
@Hairstylinstacy wrote:

Everything is looking great here! Hopefully everyone has similiar results and we can close this thread down.

But... but... I was just starting to get attached to this thread. 😞

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
brasscoe
Enthusiast - Level 2
In response to Hairstylinstacy
‎11-05-2009 03:51 PM

Looks like the problem is back.  found this post by googling 130.81.140.162

Here are my tracerts to google.com and yahoo.com  (google is slow, yahoo.com is fast)

 C:\>tracert yahoo.com

Tracing route to yahoo.com [209.131.36.159]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.5.1]
  2     8 ms     7 ms     7 ms  L101.VFTTP-142.LSANCA.verizon-gni.net [{edited for privacy}]
  3     9 ms    10 ms     9 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4    13 ms    10 ms     9 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  5    17 ms    17 ms    17 ms  so-5-3-0-0.SJC01-BB-RTR1.verizon-gni.net [130.81.19.10]
  6    21 ms    22 ms    22 ms  130.81.17.229
  7    22 ms    27 ms    21 ms  130.81.14.90
  8    22 ms    22 ms    22 ms  ae1-p160.msr1.sp1.yahoo.com [216.115.107.61]
  9    20 ms    22 ms    22 ms  te-9-1.bas-a2.sp1.yahoo.com [209.131.32.23]
 10    18 ms    19 ms    19 ms  b1.www.vip.sp1.yahoo.com [209.131.36.159]

Trace complete.

C:\>ping yahoo.com

Pinging yahoo.com [209.131.36.159] with 32 bytes of data:
Reply from 209.131.36.159: bytes=32 time=23ms TTL=54
Reply from 209.131.36.159: bytes=32 time=20ms TTL=54
Reply from 209.131.36.159: bytes=32 time=20ms TTL=54
Reply from 209.131.36.159: bytes=32 time=20ms TTL=54

Ping statistics for 209.131.36.159:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 23ms, Average = 20ms

C:\>tracert youtube.com

Tracing route to youtube.com [74.125.67.100]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.5.1]
  2     7 ms     7 ms     6 ms  L101.VFTTP-142.LSANCA.verizon-gni.net [71.254.182.1]
  3   519 ms   489 ms   476 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   435 ms   469 ms   484 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   511 ms   530 ms   539 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6    17 ms    19 ms    19 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
  7     8 ms    10 ms     9 ms  192.205.35.161
  8   528 ms   562 ms   529 ms  cr2.la2ca.ip.att.net [12.123.30.134]
  9   575 ms   582 ms   569 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 10    63 ms    64 ms    65 ms  cr1.attga.ip.att.net [12.122.28.173]
 11   541 ms   529 ms   532 ms  12.123.22.5
 12   531 ms   529 ms   527 ms  12.88.97.6
 13   499 ms   562 ms   479 ms  72.14.233.54
 14    86 ms   489 ms   477 ms  72.14.239.131
 15    90 ms    89 ms    72 ms  209.85.255.194
 16   668 ms   623 ms   636 ms  gw-in-f100.1e100.net [74.125.67.100]

Trace complete.

C:\>ping youtube.com

Pinging youtube.com [74.125.67.100] with 32 bytes of data:
Reply from 74.125.67.100: bytes=32 time=535ms TTL=50
Reply from 74.125.67.100: bytes=32 time=538ms TTL=50
Reply from 74.125.67.100: bytes=32 time=586ms TTL=50
Reply from 74.125.67.100: bytes=32 time=601ms TTL=50

Ping statistics for 74.125.67.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 535ms, Maximum = 601ms, Average = 565ms

I have a ticket open {edited for privacy}

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
jco88
Newbie
‎10-29-2009 06:12 PM

Looking really good!!

Target Name: www.google.com
         IP: 74.125.19.103
  Date/Time: 10/29/2009 6:09:21 PM

 1    0 ms  Wireless_Broadband_Router.home [192.168.1.1]
 2    4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
 3    7 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
 4    7 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27.31]
 5    7 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
 6    9 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
 7    7 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
 8    9 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
 9   11 ms  ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.52]
10   15 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
11   26 ms  ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]
12   14 ms  ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]
13   14 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
14   14 ms  [209.85.251.98]
15   16 ms  nuq04s01-in-f103.1e100.net [74.125.19.103]

Ping statistics for www.google.com
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 16ms, Maximum = 16ms, Average = 16ms

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
Torched
Enthusiast - Level 2
‎10-29-2009 06:54 PM

Still looking good at 6:50 PM in Chino Hills, Ca:

Tracing route to e3002.b.akamaiedge.net [96.6.60.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     9 ms     7 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.8
1.140.122]
  4    13 ms    12 ms    11 ms  P14-0-0.LSANCA-LCR-12.verizon-gni.net [130.81.27
.31]
  5    13 ms    12 ms    12 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
  6    14 ms    14 ms    15 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  7    16 ms    12 ms    12 ms  0.so-7-3-0.XT2.LAX7.ALTER.NET [152.63.112.62]
  8    14 ms    15 ms    15 ms  0.so-7-0-0.BR1.LAX7.ALTER.NET [152.63.112.153]
  9    13 ms    12 ms    12 ms  204.255.168.34
 10    13 ms    12 ms    14 ms  los-core-02.inet.qwest.net [205.171.32.13]
 11    12 ms    12 ms    12 ms  los-edge-01.inet.qwest.net [205.171.32.46]
 12    14 ms    12 ms    11 ms  a96-6-60-79.deploy.akamaitechnologies.com [96.6.
60.79]

Trace complete.

This looks promising...

0 Likes
Reply
An Accepted Solution is available for this post. Jump to solution.
nestacio
Enthusiast - Level 2
In response to Torched
‎10-29-2009 11:03 PM

Brett, looks like you did it. Traceroute for 11pm PST:

traceroute: Warning: www.l.google.com has multiple addresses; using 74.125.19.105

traceroute to www.l.google.com (74.125.19.105), 64 hops max, 52 byte packets

 1  myrouter (192.168.1.1)  0.691 ms  0.359 ms  0.490 ms

 2  l100.lsanca-vfttp-142.verizon-gni.net (173.55.53.1)  5.991 ms  6.878 ms  7.486 ms

 3  g4-0-6-1142.lsanca-lcr-11.verizon-gni.net (130.81.140.122)  12.728 ms  11.629 ms  12.734 ms

 4  p14-0-0.lsanca-lcr-12.verizon-gni.net (130.81.27.31)  12.729 ms  11.880 ms  9.730 ms

 5  so-4-3-0-0.lax01-bb-rtr2.verizon-gni.net (130.81.29.246)  12.491 ms  12.134 ms  16.978 ms

 6  0.so-1-2-0.xl4.lax15.alter.net (152.63.10.125)  15.809 ms  14.162 ms  15.059 ms

 7  0.ge-6-1-0.br2.lax15.alter.net (152.63.116.153)  12.520 ms  11.933 ms  12.542 ms

 8  xe-10-1-0.edge1.losangeles9.level3.net (4.68.63.129)  14.982 ms  15.149 ms  14.476 ms

 9  ae-73-70.ebr3.losangeles1.level3.net (4.69.144.116)  17.229 ms

    ae-93-90.ebr3.losangeles1.level3.net (4.69.144.244)  17.127 ms

    ae-83-80.ebr3.losangeles1.level3.net (4.69.144.180)  14.141 ms

10  ae-2.ebr3.sanjose1.level3.net (4.69.132.9)  24.137 ms  34.386 ms  35.218 ms

11  ae-93-93.csw4.sanjose1.level3.net (4.69.134.238)  24.718 ms  28.867 ms  35.464 ms

12  ae-1-69.edge1.sanjose1.level3.net (4.68.18.14)  25.218 ms  24.878 ms  24.218 ms

13  google-inc.edge1.sanjose1.level3.net (4.79.43.146)  25.222 ms  23.625 ms  25.475 ms

14  209.85.251.98 (209.85.251.98)  30.222 ms  24.358 ms  32.469 ms

15  nuq04s01-in-f105.1e100.net (74.125.19.105)  24.467 ms  24.379 ms  25.474 ms

Well done; let's keep monitoring for a few days to see if things are stable.

Neil

0 Likes
Reply