Chino Hills...AGAIN

6: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 22 ms 17 ms 6 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 555 ms 422 ms 147 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
5 7 ms 7 ms 8 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 20 ms 20 ms 21 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 22 ms 22 ms 22 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 70 ms 39 ms 24 ms verizon-gw.customer.alter.net [157.130.203.246]

9 70 ms 27 ms 77 ms 192.76.84.5
10 * * * Request timed out.

7: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 689 ms 816 ms 782 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 805 ms 746 ms 805 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.8
1.140.122]
4 825 ms 683 ms 800 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
5 527 ms 767 ms 641 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 790 ms 793 ms 802 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 867 ms 922 ms 879 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.
55.73]
8 896 ms 904 ms 924 ms verizon-gw.customer.alter.net [157.130.203.246]

9 983 ms 773 ms 675 ms 192.76.84.5
10 * * * Request timed out.

Osler

I seem to be getting much better numbers. You still having trouble?

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 6 ms 7 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 9 ms 9 ms 10 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
4 10 ms 12 ms 9 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-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 22 ms 22 ms 21 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 24 ms 27 ms 24 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.55.73]
8 28 ms 23 ms 27 ms verizon-gw.customer.alter.net [157.130.203.246]
9 27 ms 27 ms 27 ms 192.76.84.5
10 * * * Request timed out.

nestacio

Bad here also -- note that this is only an issue for LSANCA-LCR-12, which is at hop #3. Osler, you are luckily showing LCR-11 and not LCR-12, I wonder what is causing the route to choose one or the other.

Here's my traceroute as of 3:45pm today (Thurs. Nov 5):

1 myrouter (192.168.1.1) 0.927 ms 0.369 ms 0.479 ms

2 l100.lsanca-vfttp-142.verizon-gni.net (173.55.53.1) 8.485 ms 6.646 ms 7.227 ms

3 g4-0-6-1242.lsanca-lcr-12.verizon-gni.net (130.81.140.162) 575.924 ms 566.769 ms 557.9ms

4 so-4-3-0-0.lax01-bb-rtr2.verizon-gni.net (130.81.29.246) 580.083 ms 562.069 ms 577.920 ms

5 0.so-1-2-0.xl4.lax15.alter.net (152.63.10.125) 569.840 ms 544.338 ms 547.380 ms

6 0.ge-6-1-0.br2.lax15.alter.net (152.63.116.153) 9.706 ms 9.621 ms 9.724 ms

7 xe-10-1-0.edge1.losangeles9.level3.net (4.68.63.129) 559.940 ms 539.299 ms 552.916 ms

8 ae-73-70.ebr3.losangeles1.level3.net (4.69.144.116) 567.159 ms

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

ae-63-60.ebr3.losangeles1.level3.net (4.69.144.52) 14.141 ms

9 * ae-2.ebr3.sanjose1.level3.net (4.69.132.9) 559.428 ms 537.061 ms

10 ae-83-83.csw3.sanjose1.level3.net (4.69.134.234) 29.698 ms 19.134 ms 19.976 ms

11 ae-3-89.edge1.sanjose1.level3.net (4.68.18.142) 20.224 ms

ae-4-99.edge1.sanjose1.level3.net (4.68.18.206) 19.368 ms 17.132 ms

12 google-inc.edge1.sanjose1.level3.net (4.79.43.146) 522.965 ms 529.839 ms 535.237 ms

13 209.85.251.98 (209.85.251.98) 557.310 ms 564.551 ms 571.903 ms

14 nuq04s01-in-f103.1e100.net (74.125.19.103) 545.158 ms 536.577 ms 524.903 ms

I've highlighted the bad hop in red.

I was experiencing great speed again, but it only lasted for a few days.... maybe in the late evening the route uses LCR-11 only. Something tells me, they need to retire LCR-12 instead of simply rebooting it.

Verizon/Brett - if you're monitoring the boards, HELP!

Neil

ken3685a

The high latency is back again...sigh

tracert www.verizon.com

Tracing route to a1280.g.akamai.net [63.80.138.75]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 538 ms 534 ms 537 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.8
1.140.162]
4 551 ms 534 ms 517 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.246]
5 551 ms 584 ms 574 ms 0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]
6 575 ms 554 ms 557 ms 0.so-5-2-0.XL4.SJC7.ALTER.NET [152.63.48.2]
7 526 ms 524 ms 19 ms TenGigE0-7-2-0.GW3.SJC7.ALTER.NET [152.63.50.57]

8 531 ms 549 ms 567 ms 63.80.138.75

Trace complete.

same here,

5:25pm 11/5/2009 Chino Hills

lag is very bad

tracert to google.com and verizon.com as following:

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

1 4 ms 2 ms 2 ms L300.LSANCA-VFTTP-142.verizon-gni.net [71.254.182.1]
2 5 ms 4 ms 4 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.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 5 ms 4 ms 4 ms 0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
5 8 ms 824 ms 6 ms 0.ge-6-0-0.BR2.LAX15.ALTER.NET [152.63.116.149]
6 853 ms 821 ms 6 ms xe-11-0-0.edge1.SanJose3.level3.net [4.68.111.249]
7 18 ms 812 ms 818 ms ae-83-80.ebr3.LosAngeles1.Level3.net [4.69.144.180]
8 16 ms 15 ms 17 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
9 925 ms 921 ms 818 ms ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
10 831 ms 819 ms 818 ms ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
11 17 ms 16 ms 15 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
12 21 ms 20 ms 15 ms 209.85.251.98
13 858 ms 818 ms 819 ms nuq04s01-in-f103.1e100.net [74.125.19.103]

Trace complete.

C:\>tracert www.verizon.com

Tracing route to a1280.g.akamai.net [63.80.4.59]
over a maximum of 30 hops:

1 25 ms 23 ms 27 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 8 ms 6 ms 5 ms 0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
5 18 ms 15 ms 16 ms 0.ge-7-1-0.XL3.SJC7.ALTER.NET [152.63.48.254]
6 937 ms 919 ms 921 ms TenGigE0-6-1-0.GW3.SJC7.ALTER.NET [152.63.50.25]
7 856 ms 921 ms 921 ms 63.80.4.59

Trace complete.

Osler

Well, I had a couple of days of good speed, but now seeing the same problem again. I guess I got lucky on my routing for a short time. My tracert to verizon.com and google.com follow, as well as to the World of Warcraft / battle.net server, which shows terrible latency!

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 33 ms 34 ms 27 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 9 ms 9 ms 10 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
4 10 ms 10 ms 9 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
5 8 ms 10 ms 9 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 21 ms 21 ms 23 ms 0.ge-7-0-0.XT1.SAC1.ALTER.NET [152.63.49.89]
7 584 ms 607 ms 555 ms GigabitEthernet6-0-0.GW9.SAC1.ALTER.NET [152.63.55.73]
8 566 ms 592 ms 590 ms verizon-gw.customer.alter.net [157.130.203.246]
9 602 ms 584 ms 602 ms 192.76.84.5
10 * * * Request timed out.

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 6 ms 6 ms 10 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 532 ms 546 ms 527 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 567 ms 552 ms 564 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 585 ms 559 ms 567 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 13 ms 12 ms 12 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 577 ms 580 ms 589 ms 192.205.35.161
8 702 ms 663 ms 665 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 68 ms 77 ms 64 ms cr2.dlstx.ip.att.net [12.122.28.177]
10 66 ms 67 ms 66 ms cr1.attga.ip.att.net [12.122.28.173]
11 637 ms 663 ms 645 ms 12.123.22.5
12 78 ms 76 ms 74 ms 12.88.97.6
13 76 ms 71 ms 72 ms 72.14.233.56
14 692 ms 714 ms 711 ms 209.85.254.247
15 761 ms 719 ms 724 ms 209.85.255.190
16 67 ms 67 ms 67 ms gw-in-f100.1e100.net [74.125.67.100]

Trace complete.

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 6 ms 8 ms 6 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 603 ms 607 ms 626 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 593 ms 622 ms 647 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 646 ms 636 ms 612 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 12 ms 12 ms 12 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 635 ms 604 ms 619 ms 192.205.35.161
8 639 ms 17 ms 619 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 592 ms 564 ms 19 ms cr84.la2ca.ip.att.net [12.123.30.249]
10 8 ms 12 ms 12 ms gar5.la2ca.ip.att.net [12.122.129.25]
11 22 ms 24 ms 19 ms 12.122.255.74
12 547 ms 549 ms 557 ms 12.129.193.246
13 12.129.211.36 reports: Destination net unreachable.

Trace complete.

nestacio

... not LSANCA-LCR-12, which is also bad per the above posts, but a SECOND bad switch:

1 myrouter (192.168.1.1) 0.827 ms 0.383 ms 0.483 ms

2 l100.lsanca-vfttp-142.verizon-gni.net (173.55.53.1) 8.235 ms 6.726 ms 7.478 ms

3 g4-0-6-1142.lsanca-lcr-11.verizon-gni.net (130.81.140.122) 9.733 ms 9.104 ms 10.234 ms

4 so-4-3-0-0.lax01-bb-rtr1.verizon-gni.net (130.81.29.244) 9.751 ms 9.355 ms 9.754 ms

5 0.so-1-2-0.xl3.lax15.alter.net (152.63.10.133) 12.454 ms 9.080 ms 10.234 ms

6 0.ge-6-0-0.br2.lax15.alter.net (152.63.116.149) 866.997 ms

0.ge-7-0-0.br2.lax15.alter.net (152.63.116.157) 876.384 ms 886.868 ms

7 xe-10-1-0.edge1.losangeles9.level3.net (4.68.63.129) 914.650 ms

xe-11-0-0.edge1.sanjose3.level3.net (4.68.111.249) 9.117 ms

xe-10-1-0.edge1.losangeles9.level3.net (4.68.63.129) 911.654 ms

8 ae-93-90.ebr3.losangeles1.level3.net (4.69.144.244) 8.963 ms 14.790 ms

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

9 ae-2.ebr3.sanjose1.level3.net (4.69.132.9) 872.139 ms 826.294 ms 795.012 ms

10 ae-83-83.csw3.sanjose1.level3.net (4.69.134.234) 20.164 ms 31.286 ms 19.969 ms

11 ae-3-89.edge1.sanjose1.level3.net (4.68.18.142) 19.980 ms 19.381 ms 19.976 ms

12 google-inc.edge1.sanjose1.level3.net (4.79.43.146) 838.029 ms 852.378 ms 844.716 ms

13 209.85.251.98 (209.85.251.98) 817.189 ms 861.354 ms 820.013 ms

14 nuq04s01-in-f106.1e100.net (74.125.19.106) 820.000 ms 786.438 ms 803.271 ms

So check your traceroutes, it will be a problem on Hop #3 (earlier posts by others), or Hope #5 (the one in this post).

Neil

Torched

It's BACK!!!!

Chino Hills, Ca. 6:40 PM.

Very frustrating...

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

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 7 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 1040 ms 999 ms 967 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 921 ms 932 ms 929 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 926 ms 959 ms 919 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 13 ms 12 ms 11 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

7 13 ms 12 ms 12 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
8 20 ms 17 ms 16 ms ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]
9 19 ms 32 ms 34 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10 29 ms 19 ms 19 ms ae-73-73.csw2.SanJose1.Level3.net [4.69.134.230]

11 983 ms 1009 ms 1070 ms ae-2-79.edge1.SanJose1.Level3.net [4.68.18.78]
12 1054 ms 1049 ms 1017 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
13 28 ms 19 ms 19 ms 209.85.251.98
14 973 ms 987 ms 979 ms nuq04s01-in-f147.1e100.net [74.125.19.147]

Trace complete.

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 8 ms 7 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 936 ms 945 ms 952 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 983 ms 1050 ms 989 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 1019 ms 1044 ms 1052 ms 130.81.17.27
6 49 ms 47 ms 47 ms ge-3-1-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.68]
7 47 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 997 ms 970 ms 979 ms po121.ctn-core1.vzlink.com [206.46.225.18]
10 47 ms 47 ms 49 ms 206.46.228.130
11 84 ms 46 ms 47 ms 206.46.232.39

Trace complete.

Please fix permanently!

I come back from vacation and the network is broke AGAIN??? Am I not allowed to go on vacation anymore?

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 988 ms 994 ms 970 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 966 ms 927 ms 941 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 959 ms 982 ms 982 ms 130.81.17.27
6 46 ms 47 ms 49 ms ge-3-1-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.68]
7 47 ms 47 ms 47 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
8 46 ms 46 ms 47 ms po1.ctn-border1.vzlink.com [206.46.225.85]
9 1029 ms 1027 ms 1001 ms po121.ctn-core1.vzlink.com [206.46.225.18]
10 49 ms 47 ms 47 ms 206.46.228.130
11 51 ms 49 ms 47 ms 206.46.232.39

Trace complete.

Traceroute: 11/5/09, 6:41pm.

I called tech support and they opened up a ticket for me. Last month when we had this problem, they said only a few people were on their "group ticket" for this issue, so it didn't seem like a big problem to them. If you are experiencing high latency in the area, I recommend calling tech support so they know you're affected, and ask for a ticket number. That way they know it's affecting more than just a few people.

Current stats: 11/5/09, 7:45pm...

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 960 ms 959 ms 967 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 1016 ms 1039 ms 984 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 1070 ms 1047 ms 1019 ms 130.81.17.27
6 46 ms 47 ms 46 ms ge-3-1-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.68]
7 126 ms 50 ms 47 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
8 48 ms 47 ms 62 ms po1.ctn-border1.vzlink.com [206.46.225.85]
9 46 ms 46 ms 47 ms po121.ctn-core1.vzlink.com [206.46.225.18]
10 51 ms 47 ms 47 ms 206.46.228.130
11 1108 ms 1067 ms 1110 ms 206.46.232.39

Trace complete.

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

9 907 ms 874 ms 833 ms 192.76.84.5
10 * * * Request timed out.

yup, same latency issue again. called it in and the FIOS support person wants to send me a new router... how funny or rather illogical is that. i told him a bunch of people in chino hills is having the same exact problem from days/weeks before. he said 'maybe a bunch of us have bad routers'. That just raised my blood pressure!!!

anyway, here's my trace....

C:\>tracert www.google.com

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

over a maximum of 30 hops:

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

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

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

4 1109 ms 1147 ms 1164 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]

5 1127 ms 1140 ms 1112 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]

6 9 ms 9 ms 9 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]

7 1107 ms 1082 ms 1067 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]

8 1104 ms 1092 ms 1089 ms ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.116]

9 19 ms 17 ms 17 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]

10 1153 ms 1089 ms 1084 ms ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]

11 24 ms 24 ms 27 ms ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]

12 18 ms 17 ms 17 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]

13 16 ms 17 ms 17 ms 209.85.251.98

14 16 ms 17 ms 1082 ms nuq04s01-in-f147.1e100.net [74.125.19.147]

Trace complete.

1500ms ping !!!!

C:\>tracert www.google.com

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

1 24 ms 28 ms 119 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 7 ms 5 ms 4 ms 0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
5 8 ms 1693 ms 6 ms 0.ge-6-0-0.BR2.LAX15.ALTER.NET [152.63.116.149]
6 7 ms 6 ms 1744 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
7 1725 ms 1740 ms 1638 ms ae-83-80.ebr3.LosAngeles1.Level3.net [4.69.144.180]
8 25 ms 19 ms 15 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
9 1614 ms 1740 ms 1740 ms ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
10 1638 ms 1637 ms 1638 ms ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
11 15 ms 15 ms 15 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
12 25 ms 17 ms 18 ms 209.85.251.98
13 1680 ms 1635 ms 1531 ms nuq04s01-in-f147.1e100.net [74.125.19.147]

Trace complete.

Osler

Still with bad latency. I spoke with a guy named Oliver at support, who at least knew what a tracert was and asked me which hop I was having trouble with! A ticket was opened for me as well. Here's my latest tracert: As before, anything going through G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162] is bad.

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 7 ms 7 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 556 ms 504 ms 535 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 541 ms 549 ms 562 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 597 ms 562 ms 564 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 21 ms 19 ms 17 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
7 550 ms 544 ms 551 ms 192.205.35.161
8 640 ms 649 ms 604 ms cr2.la2ca.ip.att.net [12.123.30.134]
9 66 ms 67 ms 64 ms cr2.dlstx.ip.att.net [12.122.28.177]
10 67 ms 74 ms 70 ms cr1.attga.ip.att.net [12.122.28.173]
11 713 ms 654 ms 661 ms 12.123.22.5
12 63 ms 67 ms 64 ms 12.88.97.6
13 65 ms 65 ms 64 ms 72.14.233.56
14 681 ms 126 ms 67 ms 209.85.254.243
15 731 ms 752 ms 748 ms 209.85.253.145
16 68 ms 67 ms 66 ms yx-in-f100.1e100.net [74.125.45.100]

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 8 ms 6 ms 7 ms L100.LSANCA-VFTTP-142.verizon-gni.net
3 8 ms 9 ms 10 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
4 9 ms 10 ms 10 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
5 48 ms 46 ms 47 ms so-7-3-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.19.125]
6 47 ms 47 ms 47 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
7 46 ms 47 ms 46 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 46 ms 46 ms 47 ms 206.46.232.39

Trace complete.

Whats up everybody! I did get your private messages & will escalate this issue again today! If you could keep posting some more trace routes to verizon.net also that would be helpful. & I beleive Misterjefferson you mentioned you opened up a group ticket? If you could private message me that ticket # . I would apprciate it Thanks All! will update shortly!

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

as usual, in the morning, things are fine since it doesn't go thru the troubled router... have to wait till tonight to post trace routes again...

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

Torched

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.

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

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.

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.

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

nestacio

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

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

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.

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

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

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

KlassiK

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

1 46 ms <1 ms 46 ms Wireless_Broadband_Router.home [192.168.1.1]
2 53 ms 53 ms 53 ms L100.LSANCA-VFTTP-83.verizon-gni.net [71.189.63.
1]
3 58 ms 59 ms 58 ms G9-0-1183.LSANCA-LCR-11.verizon-gni.net [130.81.
107.214]
4 98 ms 4294967262 ms 12 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [
130.81.29.244]
5 13 ms 58 ms 58 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 89 ms 88 ms 89 ms 0.so-7-1-0.XL3.DEN4.ALTER.NET [152.63.88.54]
7 87 ms 89 ms 42 ms POS6-0.GW3.DEN4.ALTER.NET [152.63.72.69]
8 41 ms 88 ms 88 ms internap-gw.customer.alter.net [157.130.162.54]

9 38 ms 86 ms 39 ms border8.ge4-1-bbnet2.den.pnap.net [216.52.40.77]

10 45 ms 49 ms 98 ms internetsearch-4.border8.den.pnap.net [66.151.16
3.98]
11 * * * Request timed out.
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 * * * Request timed out.
20 * * * Request timed out.
21 *

Keeps timing out...

Download Speed: 9781 kbps (1222.6 KB/sec transfer rate)
Upload Speed: 1811 kbps (226.4 KB/sec transfer rate)

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

@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

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.

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.

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

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..

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

sure Bret, will post traces tonight. thanks.

10:15am 11/10/2009

I tried this morning, looks like everything back to normal, following website loaded as usual

I will post tracert if tonight something wrong again.

thank you Brett

-David

response time seems fine last night so i guess the problem was fixed....

Hey guys could you please keep any eye on it, I will do the same & let me know if any latency comes back on the LCR or unable to get to websites. Thanks! Brett