High latency and poor speed tests lately
MisterJefferson
Enthusiast - Level 3

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
MisterJefferson
Enthusiast - Level 3

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
jco88
Newbie

From chino hills... this is my latest trace. as you can see, the network latency issue is NOT FIXED.  It is getting very frustrating dealing with this and talking to FIOS support coz they don't seem to want to do anything about it.   Not sure what part of  ' several Chino Hills resident's are having the same problem' don't they understand. It's not a PC, router, config on our side but it's their so called 'FIBER' optic network that is messed up.  It's been 2 weeks now and nothing!!!  

$ tracert latimes.com

Tracing route to latimes.com [144.142.224.43]

over a maximum of 30 hops:

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

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

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


  4   548 ms   556 ms   535 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]

  5   506 ms   532 ms   537 ms  0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]

  6   507 ms   513 ms   516 ms  0.so-7-0-0.XL4.LAX15.ALTER.NET [152.63.112.61]

  7   516 ms   508 ms   511 ms  POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]

  8    11 ms    11 ms    11 ms  internapGIGE-gw.customer.alter.net [157.130.236.110]

  9    21 ms    22 ms    22 ms  border21.po1-20g-bbnet1.lax.pnap.net [216.52.255.38]

 10     *        *        *     Request timed out.

 11   484 ms   469 ms   491 ms  secure.latimes.com [144.142.224.43]

Trace complete.

$ tracert verizon.net

Tracing route to verizon.net [206.46.232.39]

over a maximum of 30 hops:

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

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

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

  4   459 ms   441 ms   423 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]

  5   488 ms   421 ms   412 ms  130.81.17.27

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

  7    42 ms    44 ms    37 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]

  8    65 ms    57 ms    61 ms  po1.ctn-border1.vzlink.com [206.46.225.85]

  9   413 ms   417 ms   418 ms  po121.ctn-core1.vzlink.com [206.46.225.18]

 10   390 ms   406 ms   387 ms  206.46.228.130

 11    53 ms    59 ms    57 ms  206.46.232.39

0 Likes
Reply
jco88
Newbie

by the way, if you haven't tried it... you can use pingplotter to do trace and you can visually see where the latency is... you can configure it to trace at a certain number of intervals to get a good sampling and can send to a tech guy for analysis.

get it from  http://www.pingplotter.com/

0 Likes
Reply
MisterJefferson
Enthusiast - Level 3

It doesn't look like maintenance fixed my issue.  Seems worse tonight (10/27, 8:05pm):

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     8 ms     7 ms     7 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3  1111 ms  1076 ms  1104 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4  1054 ms  1047 ms   982 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5  1028 ms  1037 ms   981 ms  130.81.17.27
  6    67 ms    77 ms    77 ms  so-7-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.12]
  7   127 ms    97 ms    85 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  8    71 ms    69 ms    77 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  9  1030 ms  1007 ms   992 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 10    75 ms    75 ms    79 ms  206.46.228.130
 11    67 ms    63 ms    58 ms  206.46.232.39

Trace complete.

0 Likes
Reply
ken3685a
Newbie

I'm also from Chino Hills and I'm having the same problem for the past 10 days or so. I called the tech support this morning and they pretty much blame my system for the slow down. If they don't resolve this problem soon, I might have to shop around for a new ISP.


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  Wireless_Broadband_Router.home [192.168.1.1]
  2     9 ms     4 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3   705 ms   734 ms   726 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
  4   726 ms   768 ms   760 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
  5   733 ms     *      812 ms  0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]
  6   795 ms   779 ms   824 ms  POS7-0.BR2.LAX7.ALTER.NET [152.63.112.149]
  7   781 ms   774 ms   777 ms  p64-6-1-3.r20.lsanca03.us.bb.gin.ntt.net [129.25
0.8.205]
  8   760 ms   805 ms   823 ms  po-1.r00.lsanca03.us.bb.gin.ntt.net [129.250.5.2
54]
  9   837 ms   842 ms   818 ms  a69-192-44-79.deploy.akamaitechnologies.com [69.
192.44.79]

Trace complete.

0 Likes
Reply
Hairstylinstacy
Enthusiast - Level 1

Taken at 9:45pm

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

  9  1112 ms  1153 ms  1167 ms  192.76.84.5

Called Verizon support again to see if there was any more information to obtain and after a lengthy conversation I was told that the problem is on my end, and that Verizon's service is fine...

0 Likes
Reply
MisterJefferson
Enthusiast - Level 3

@Hairstylinstacy wrote:

Called Verizon support again to see if there was any more information to obtain and after a lengthy conversation I was told that the problem is on my end, and that Verizon's service is fine...


Yeah, everything's fine from your home to the central office. The problem is further up the river.  The techs on the phone don't seem to understand that.  Even the field tech that came out to the house kept trying to say it wasn't their problem and said he'd have his supervisor call me.  Never got a call.

0 Likes
Reply
ken3685a
Newbie

As of 10:16pm, it's getting worse. This is getting ridiculous.... I will call the tech support tomorrow and if they still in denial stage, time to cancel the service.

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  Wireless_Broadband_Router.home [192.168.1.1]
  2     3 ms     4 ms     4 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
  3  1151 ms  1159 ms  1139 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
  4  1174 ms  1134 ms  1139 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
  5  1174 ms  1162 ms  1137 ms  0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]
  6  1151 ms  1164 ms  1162 ms  POS7-0.BR2.LAX7.ALTER.NET [152.63.112.149]
  7  1219 ms  1179 ms  1172 ms  p64-6-1-3.r20.lsanca03.us.bb.gin.ntt.net [129.25
0.8.205]
  8  1191 ms     *     1253 ms  po-1.r00.lsanca03.us.bb.gin.ntt.net [129.250.5.2
54]
  9  1219 ms  1254 ms  1242 ms  a69-192-44-79.deploy.akamaitechnologies.com [69.
192.44.79]

Trace complete.

0 Likes
Reply
dwoo
Enthusiast - Level 2

I am from Chino Hills, these recent two weeks I am getting slow internet browsing. Here is my tracert to google.com @ 10/27 11:45PM

I guess the problem would be 130.8.1.140.162

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

  1     2 ms     1 ms     2 ms  L300.LSANCA-VFTTP-142.verizon-gni.net [71.254.182.1]
  2   814 ms   818 ms   732 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  3   841 ms   716 ms   675 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  4   740 ms   714 ms   716 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  5     8 ms     5 ms     7 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
  6   749 ms   716 ms   716 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  7   841 ms   820 ms   817 ms  ae-82-80.ebr2.LosAngeles1.Level3.net [4.69.144.179]
  8   840 ms   820 ms   817 ms  ae-2.ebr2.SanJose1.Level3.net [4.69.132.13]
  9    36 ms    34 ms    33 ms  ae-7.ebr1.Seattle1.Level3.net [4.69.132.50]
 10   790 ms   822 ms   815 ms  ae-1-51.edge1.Seattle3.Level3.net [4.68.105.12]
 11   735 ms   716 ms   716 ms  GOOGLE-INC.edge1.Seattle3.Level3.net [4.59.232.34]
 12    37 ms    34 ms    37 ms  209.85.249.32
 13    39 ms    38 ms    38 ms  72.14.239.12
 14   776 ms   818 ms   819 ms  209.85.250.146
 15    44 ms    42 ms   857 ms  216.239.48.165
 16    51 ms  1034 ms    45 ms  72.14.232.10
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23  ^C

Also this is tracert verizon.com, all looks good if using LCR-11 instead of 12, but still something high ping,

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

  1     3 ms     1 ms     2 ms  L300.LSANCA-VFTTP-142.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     6 ms     4 ms     4 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  4    10 ms     5 ms     6 ms  0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
  5    19 ms    17 ms    17 ms  0.so-5-0-0.XT1.SAC1.ALTER.NET [152.63.0.98]
  6   960 ms  1024 ms  1022 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.55.73]
  7   920 ms   921 ms   921 ms  verizon-gw.customer.alter.net [157.130.203.246]
  8    24 ms    17 ms    19 ms  192.76.84.5
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *     ^C

hope this help and wish Verizon fix this soon,

0 Likes
Reply
VZ_Brett
Contributor - Level 2

All, we do have a group ticket opened up on that router. I just updated the new trace routes & waiting a reply back, once i get one will update here. Thanks again

0 Likes
Reply
aravoth
Newbie

It's not just chino hills, Like I said earlier, I'm in Portland, Oregon, same problem. {please keep your posts courteous}. This has been going on for way too long. Fix the fracken network already. I'm not calling tech support again. If I hear one more **bleep** tell me to push the reset button on that {edit} router verizon supplies, I am going to puke.

If I wanted DSL speeds, I would have ordered DSL.

Additionaly, Verizon needs to hire people for tech support that can read above a third grade level, and have a strong command of the english language. When a tech support person says, "I'mma putch ya through ta billin' soze you can axe em' what ta do", it doesn't inspire confidence, both in the person that said that, and the person that hired him.

Billing can not fix this, and twice now, Tech support has tried to transfer me to billing.

0 Likes
Reply
Hairstylinstacy
Enthusiast - Level 1
I can understand that problems arise, and need to be tracked down, isolated and fixed. It wouldn't be so bad if Tech support(outsourced I assume) would at least admit that there is a problem instead of blaming the customers each time. Honestly if it wasn't for Brett posting in this thread notifying us that things are acknowledged, and being escalated to the proper departments I would have canceled already and went back to AT&T Uverse.
0 Likes
Reply
dwoo
Enthusiast - Level 2

the latest tracert (10-28-2009, 2:15pm) from Chino Hills,

to google.com

Tracing route to google.com {edited for privacy}
over a maximum of 30 hops:

  1     2 ms     2 ms     1 ms  L101.VFTTP-142.LSANCA.verizon-gni.net [71.254.18
2.1]
  2   279 ms   205 ms   203 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
  3   216 ms   199 ms   204 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
  4   220 ms   307 ms   305 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  5     7 ms     5 ms     6 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]

  6     7 ms     5 ms     5 ms  192.205.35.161
  7    62 ms    60 ms    63 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   201 ms   304 ms   306 ms  cr1.attga.ip.att.net [12.122.28.173]
 10   190 ms   197 ms   270 ms  12.123.22.5
 11   394 ms   408 ms   306 ms  12.88.97.6
 12    64 ms    60 ms    61 ms  72.14.233.56
 13   394 ms   304 ms   409 ms  209.85.254.249
 14    64 ms    61 ms    71 ms  64.233.174.46
 15   300 ms   307 ms   306 ms  gw-in-f100.1e100.net [74.125.67.100]

Trace complete.

to verizon.com

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

  1     2 ms     1 ms     1 ms  L101.VFTTP-142.LSANCA.verizon-gni.net [71.254.18
2.1]
  2     6 ms     4 ms     5 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
  3     6 ms     5 ms     4 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
  4     8 ms     6 ms     6 ms  0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
  5    18 ms    17 ms    17 ms  0.so-5-0-0.XT1.SAC1.ALTER.NET [152.63.0.98]
  6   270 ms   204 ms   204 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
  7   241 ms   204 ms   205 ms  verizon-gw.customer.alter.net [157.130.203.246]

  8    22 ms    17 ms    18 ms  192.76.84.5
  9     *        *        *     Request timed out.
 10     *     ^C

****** much much better than yesterday, good job ******

(well, if LCR-12 can lower to 100 ping that will be better 😛 )

0 Likes
Reply
Caution
Newbie

Hello all.... Well to keep consistent i am another user/subscriber here in the Chino/Chino hills area.  and as like everyone else i have severe latency while surfing the net or playing online game.   below are some of my tracert print outs.....

Target Name: www.download.com
         IP: 216.239.122.164
  Date/Time: 10/28/2009 3:18:16 PM

 1    1 ms    3 ms    3 ms  Wireless_Broadband_Router.home [192.168.1.1]
 2    7 ms   10 ms    9 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
 3  511 ms  507 ms  424 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
 4  507 ms  519 ms  430 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
 5  500 ms  517 ms  426 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
 6  495 ms  524 ms  429 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
 7   18 ms   11 ms   14 ms  [192.205.35.161]
 8   50 ms   46 ms   46 ms  cr2.la2ca.ip.att.net [12.123.30.134]
 9  530 ms  562 ms  460 ms  cr2.dlstx.ip.att.net [12.122.28.177]
10  561 ms  561 ms  468 ms  gar10.dlstx.ip.att.net [12.122.138.125]
11  542 ms  557 ms  473 ms  [12.87.121.22]
12  533 ms  551 ms  476 ms  c18-rb-gtm1-tron-xw-lb.cnet.com [216.239.122.164]

Ping statistics for www.download.com
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 476ms, Maximum = 551ms, Average = 520ms

Target Name: www.download.com
         IP: 216.239.122.176
  Date/Time: 10/28/2009 3:34:06 PM

 1    1 ms    1 ms  Wireless_Broadband_Router.home [192.168.1.1]
 2    8 ms    9 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
 3  336 ms  340 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
 4  334 ms  342 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
 5  330 ms  336 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
 6  332 ms  336 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
 7   11 ms   16 ms  [192.205.35.161]
 8   49 ms   50 ms  cr2.la2ca.ip.att.net [12.123.30.134]
 9  329 ms  373 ms  cr2.dlstx.ip.att.net [12.122.28.177]
10  334 ms  352 ms  gar10.dlstx.ip.att.net [12.122.138.117]
11  341 ms  346 ms  [12.87.121.22]
12  334 ms  343 ms  c18-rb-gtm3-tron-xw-lb.cnet.com [216.239.122.176]

Ping statistics for www.download.com
Packets: Sent = 2, Received = 2, Lost = 0 (0.0%)
Round Trip Times: Minimum = 334ms, Maximum = 343ms, Average = 338ms

When playing online games my latency starts at about 400ms...... and by 9pm...it will be near 5000ms....

Hopefully another person posting here will help.....

thanks

0 Likes
Reply
dwoo
Enthusiast - Level 2

4:50pm can't believe lag is back !! (10/28/2009)

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

  1     2 ms     1 ms     2 ms  L101.VFTTP-142.LSANCA.verizon-gni.net{edited for privacy}
  2   563 ms   513 ms   510 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  3   533 ms   511 ms   511 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  4   534 ms   511 ms   511 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  5   431 ms   512 ms   411 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
  6     9 ms     5 ms     5 ms  192.205.35.161
  7    63 ms    61 ms    61 ms  cr2.la2ca.ip.att.net [12.123.30.134]
  8   105 ms    60 ms    61 ms  cr2.dlstx.ip.att.net [12.122.28.177]
  9   490 ms   408 ms   410 ms  cr1.attga.ip.att.net [12.122.28.173]
 10   442 ms   409 ms   409 ms  12.123.22.5
 11   432 ms   409 ms   409 ms  12.88.97.6
 12   532 ms   513 ms   511 ms  72.14.233.54
 13   535 ms   513 ms   509 ms  72.14.232.215
 14   532 ms   511 ms   514 ms  209.85.253.145
 15   639 ms   716 ms   616 ms  yx-in-f100.1e100.net [74.125.45.100]

Trace complete.

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

  1     7 ms     2 ms     2 ms  L101.VFTTP-142.LSANCA.verizon-gni.net [71.254.182.1]
  2     6 ms     3 ms     4 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  3     9 ms     4 ms     4 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  4     7 ms     6 ms     6 ms  0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
  5    19 ms    17 ms    21 ms  0.so-5-0-0.XT1.SAC1.ALTER.NET [152.63.0.98]
  6   459 ms   409 ms   408 ms  GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.55.73]
  7   433 ms   406 ms   409 ms  verizon-gw.customer.alter.net [157.130.203.246]
  8    20 ms    17 ms    18 ms  192.76.84.5
  9     *        *        *     Request timed out.
 10     *     ^C

0 Likes
Reply
Osler
Enthusiast - Level 1

My current tracerts are below. Practically speaking (i.e. in-game and downloading), connection remains very poor.

Tracing route to us.logon.battle.net [12.129.206.130]
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  L100.LSANCA-VFTTP-142.verizon-gni.net
  3   246 ms   254 ms   247 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   287 ms   287 ms   297 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   329 ms   324 ms   337 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6    12 ms    12 ms    22 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
  7   305 ms   302 ms   292 ms  192.205.35.161
  8    11 ms    12 ms   294 ms  cr2.la2ca.ip.att.net [12.123.30.134]
  9     9 ms    12 ms    12 ms  gar4.la2ca.ip.att.net [12.122.129.169]
 10    12 ms    12 ms    12 ms  12.122.255.70
 11   283 ms   281 ms   292 ms  12.129.193.254
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19  12.129.211.36  reports: Destination net unreachable.

Trace complete.

Tracing route to vpn.pvhmc.org [65.218.207.68]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     5 ms     7 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net
  3   351 ms   334 ms   347 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   351 ms   352 ms   349 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   371 ms   357 ms   394 ms  0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
  6   424 ms   409 ms   416 ms  0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
  7   438 ms   422 ms   399 ms  GigabitEthernet7-0-0.GW7.LAX7.ALTER.NET [152.63.118.53]
  8    15 ms    15 ms    14 ms  pvhmc-gw.customer.alter.net [157.130.233.98]
  9    21 ms    16 ms    19 ms  vpn.pvhmc.org [65.218.207.68]

Trace complete.

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     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net
  3    10 ms    10 ms     9 ms  G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
  4    10 ms     9 ms    10 ms  so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
  5    47 ms    47 ms    48 ms  so-3-3-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.18]
  6   129 ms    84 ms    46 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  7    48 ms    47 ms    47 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  8    47 ms    47 ms    47 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
  9    46 ms    47 ms    47 ms  206.46.228.130
 10    45 ms    47 ms    47 ms  206.46.232.39

Trace complete.

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

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     7 ms     7 ms     6 ms  L100.LSANCA-VFTTP-142.verizon-gni.net
  3   473 ms   469 ms   455 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   391 ms   396 ms   402 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   377 ms   392 ms   362 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6    10 ms    12 ms    12 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
  7   380 ms     *      418 ms  192.205.35.161
  8   389 ms   397 ms   424 ms  cr2.la2ca.ip.att.net [12.123.30.134]
  9    63 ms    65 ms    67 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 10    65 ms    64 ms    65 ms  cr1.attga.ip.att.net [12.122.28.173]
 11   376 ms   379 ms   390 ms  12.123.22.5
 12    66 ms    64 ms    65 ms  12.88.97.6
 13   480 ms   481 ms   527 ms  72.14.233.54
 14     *       71 ms    77 ms  72.14.239.127
 15    80 ms    72 ms    72 ms  64.233.174.46
 16    70 ms    66 ms    67 ms  gw-in-f100.1e100.net [74.125.67.100]

Trace complete.

0 Likes
Reply
Torched
Enthusiast - Level 2

6:00 PM 10/28/2009 problem still continues in Chino Hills, Ca.

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

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     8 ms     6 ms     7 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
  3   286 ms   282 ms   281 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   303 ms   305 ms   266 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   236 ms   236 ms   239 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  6    11 ms    12 ms    12 ms  0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

  7    24 ms    24 ms    29 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  8   250 ms   239 ms   252 ms  ae-93-90.ebr3.LosAngeles1.Level3.net [4.69.144.244]
  9    29 ms    34 ms    37 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10   250 ms   256 ms   245 ms  ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]

 11   251 ms   254 ms   252 ms  ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]
 12   299 ms   270 ms   314 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 13    31 ms    19 ms    34 ms  209.85.251.98
 14   282 ms   316 ms   327 ms  nuq04s01-in-f99.1e100.net [74.125.19.99]

Trace complete.

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

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     8 ms     7 ms    14 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
  3   366 ms   359 ms   355 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   342 ms   330 ms   327 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   322 ms   424 ms   350 ms  0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
  6   369 ms   367 ms   359 ms  0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
  7   380 ms   372 ms   367 ms  POS7-0.BR2.LAX7.ALTER.NET [152.63.112.149]
  8   362 ms   361 ms   355 ms  p64-6-1-3.r20.lsanca03.us.bb.gin.ntt.net [129.250.8.205]
  9   361 ms   372 ms   402 ms  as-0.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.96]
 10   405 ms   396 ms   375 ms  po-4.r03.snjsca04.us.bb.gin.ntt.net [129.250.4.78]
 11   400 ms   392 ms   429 ms  a96-6-236-79.deploy.akamaitechnologies.com [96.6.236.79]

Trace complete.

0 Likes
Reply
Caution
Newbie

Hello again... Here is another latency report from Chino/Chino Hills....  Test done at approx 8pm

Target Name: www.google.com
         IP: 74.125.19.104
  Date/Time: 10/28/2009 8:02:32 PM

 1    3 ms    3 ms  Wireless_Broadband_Router.home [192.168.1.1]
 2    8 ms    8 ms  L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
 3  471 ms  495 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
 4  471 ms  498 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
 5  475 ms  503 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
 6  468 ms  523 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
 7   16 ms   10 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
 8   13 ms   15 ms  ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]
 9   27 ms   30 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10  498 ms  538 ms  ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]
11   19 ms   20 ms  ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]
12   24 ms   18 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
13   21 ms  524 ms  [209.85.251.98]
14  494 ms   20 ms  nuq04s01-in-f104.1e100.net [74.125.19.104]

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

SIGH!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

0 Likes
Reply
dwoo
Enthusiast - Level 2

8:10pm getting worse ... 😞

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

  1     2 ms     2 ms     1 ms  L300.LSANCA-VFTTP-142.verizon-gni.net [hide for privacy]
  2   639 ms   615 ms   613 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  3   629 ms   613 ms   614 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  4   626 ms   614 ms   716 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  5     8 ms     6 ms     9 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
  6   603 ms   643 ms   616 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  7   614 ms   602 ms   639 ms  ae-82-80.ebr2.LosAngeles1.Level3.net [4.69.144.179]
  8   623 ms   646 ms   717 ms  ae-2.ebr2.SanJose1.Level3.net [4.69.132.13]
  9    35 ms    33 ms    33 ms  ae-7.ebr1.Seattle1.Level3.net [4.69.132.50]
 10   677 ms   610 ms   718 ms  ae-1-51.edge1.Seattle3.Level3.net [4.68.105.12]
 11   626 ms   614 ms   719 ms  GOOGLE-INC.edge1.Seattle3.Level3.net [4.59.232.34]
 12    59 ms     *       36 ms  209.85.249.32
 13    39 ms    38 ms    38 ms  72.14.239.12
 14   676 ms   717 ms   715 ms  216.239.48.32
 15    42 ms   596 ms   613 ms  216.239.48.165
 16    42 ms   593 ms   613 ms  72.14.232.2
 17    42 ms    39 ms    41 ms  pw-in-f100.1e100.net [74.125.53.100]

Trace complete.

0 Likes
Reply
nestacio
Enthusiast - Level 2

Thanks Brett for being completely professional and moving things forward. I'll continue to do my part, here is my traceroute update for 9pm tonight (wed. night):

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

over a maximum of 30 hops:


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

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

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

  4   713 ms   734 ms   739 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]

  5   782 ms   754 ms   706 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]

  6    10 ms     9 ms    10 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]

  7   756 ms   699 ms   711 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]

  8   696 ms   700 ms   682 ms  ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]

  9   728 ms   699 ms   679 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]

 10   658 ms   639 ms   652 ms  ae-93-93.csw4.SanJose1.Level3.net [4.69.134.238]

 11    21 ms    19 ms    34 ms  ae-4-99.edge1.SanJose1.Level3.net [4.68.18.206]

 12   660 ms   666 ms   654 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]

 13   652 ms   672 ms   679 ms  209.85.251.98

 14   698 ms   710 ms   689 ms  nuq04s01-in-f103.1e100.net [74.125.19.103]


Trace complete.

Hop #3 at LSANCA-LCR-12.verizon-gni.net [130.81.140.162] is still returning high ping (~700ms); thanks for looking into it.

Neil

0 Likes
Reply
MisterJefferson
Enthusiast - Level 3

Update 10/28/09 at 9:09pm.  Still does not appear to be fixed.

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     6 ms     7 ms     7 ms  xxxx.xxxxx-xxxxx-xxx.verizon-gni.net [173.55.xxx.xxx]
  3   724 ms   714 ms   741 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  4   705 ms   681 ms   659 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  5   727 ms   719 ms   702 ms  130.81.17.27
  6    45 ms    47 ms    65 ms  so-1-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.66]
  7    46 ms    48 ms    47 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
  8    47 ms    47 ms    47 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  9   777 ms   736 ms   734 ms  po121.ctn-core1.vzlink.com [206.46.225.18]
 10    47 ms    51 ms    48 ms  206.46.228.130
 11    47 ms    49 ms    47 ms  206.46.232.39

Trace complete.


0 Likes
Reply
dwoo
Enthusiast - Level 2

9:35pm, now over 1k ping ...

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

  1     2 ms     1 ms     1 ms  L300.LSANCA-VFTTP-142.verizon-gni.net [private]
  2  1168 ms  1126 ms  1126 ms  G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
  3  1124 ms  1126 ms  1126 ms  so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
  4  1124 ms  1127 ms  1025 ms  0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
  5     6 ms     6 ms     5 ms  0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
  6  1121 ms  1024 ms   982 ms  xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
  7    16 ms    17 ms    17 ms  ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.52]
  8    25 ms    36 ms    53 ms  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
  9  1045 ms  1137 ms  1126 ms  ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
 10  1122 ms  1124 ms  1125 ms  ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
 11    15 ms    19 ms    33 ms  GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
 12    18 ms    18 ms    17 ms  209.85.251.98
 13    17 ms    15 ms    15 ms  nuq04s01-in-f106.1e100.net [74.125.19.106]

Trace complete.

0 Likes
Reply