- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here are my Ping times for a trace route.............which are good but on a speed test from speedtest.net it shows me with a 1.2mb download and 22.1 mb upload. Something wrong with my line!
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\The WEIMDADDY>tracert www.verizon.com
Tracing route to a1280.g.akamai.net [65.200.11.154]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms WEIMDADDY.home [192.168.1.1]
2 3 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 6 ms 7 ms 7 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.244]
5 6 ms 7 ms 7 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
6 6 ms 7 ms 7 ms 0.so-7-1-0.XL3.LAX15.ALTER.NET [152.63.1.226]
7 8 ms 7 ms 9 ms TenGigE0-6-1-0.GW4.LAX15.ALTER.NET [152.63.114.2
09]
8 11 ms 9 ms 9 ms a65.200.11.154.deploy.akamaitechnologies.com [65
.200.11.154]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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}
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5:30pm
Looks like something bad back again (130.91.140.162)
C:\>tracert www.google.com
Tracing route to www.l.google.com [74.125.19.104]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms L300.LSANCA-VFTTP-142.verizon-gni.net [71.254.182.1]
2 735 ms 716 ms 818 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
3 774 ms 782 ms 716 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
4 842 ms 819 ms 714 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
5 7 ms 5 ms 5 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
6 731 ms 716 ms 717 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
7 10 ms 12 ms 17 ms ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.52]
8 18 ms 17 ms 20 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
9 811 ms 818 ms 820 ms ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
10 739 ms 819 ms 819 ms ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
11 16 ms 14 ms 15 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
12 24 ms 17 ms 18 ms 209.85.251.98
13 737 ms 793 ms 817 ms nuq04s01-in-f104.1e100.net [74.125.19.104]
Trace complete.
C:\>tracert www.verizon.com
Tracing route to a1280.g.akamai.net [65.197.197.34]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms L300.LSANCA-VFTTP-142.verizon-gni.net [71.254.182.1]
2 797 ms 818 ms 820 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
3 739 ms 819 ms 818 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
4 840 ms 818 ms 819 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
5 841 ms 716 ms 819 ms 0.so-7-1-0.XL4.LAX15.ALTER.NET [152.63.1.242]
6 14 ms 8 ms 7 ms TenGigE0-7-1-0.GW4.LAX15.ALTER.NET [152.63.114.225]
7 10 ms 6 ms 7 ms a65.197.197.34.deploy.akamaitechnologies.com [65
.197.197.34]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seems to be affecting Chino Hills for sure, called Verizon again, no update, said I could call back tomorrow morning. This sucks. I have verizon business and a vpn server with 30+ clients, 3/4 of them having slow connection speeds now. Maybe it's time to go back to Time Warner.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This problem is NOT resolved and should not be marked as such. It was temporarily resolved but is clearly back again.
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.
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The trouble ticket they gave me was, {edited for privacy} calling again now to get status.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
why is this problem back again!!!!! This LSANCA-LCR-12 router/device is MESSED UP again!!
Target Name: latimes.com
IP: 144.142.224.43
Date/Time: 11/5/2009 7:44:51 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 1010 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 1011 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 1008 ms 0.so-6-2-0.XT2.LAX7.ALTER.NET [152.63.112.49]
6 1006 ms 0.so-7-0-0.XL4.LAX15.ALTER.NET [152.63.112.61]
7 1008 ms POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]
8 10 ms internapGIGE-gw.customer.alter.net [157.130.236.110]
9 11 ms border21.po1-20g-bbnet1.lax.pnap.net [216.52.255.38]
10 * [-]
11 996 ms secure.latimes.com [144.142.224.43]
Ping statistics for latimes.com
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 996ms, Maximum = 996ms, Average = 996ms
Target Name: hulu.com
IP: 69.22.138.131
Date/Time: 11/5/2009 7:45:18 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 1056 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 1061 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 6 ms [130.81.17.203]
6 32 ms ae0-308.cr1.lax1.us.nlayer.net [69.31.127.45]
7 56 ms xe-1-2-0.cr1.sjc1.us.nlayer.net [69.22.142.54]
8 28 ms po1-30g.ar2.sjc1.us.nlayer.net [69.22.143.138]
9 16 ms [69.22.138.131]
Ping statistics for hulu.com
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 16ms, Maximum = 16ms, Average = 16ms
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
another trace..............
Target Name: www.verizon.net
IP: 96.6.236.79
Date/Time: 11/5/2009 7:48:06 PM
1 0 ms 0 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 1147 ms 937 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 1147 ms 926 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 1145 ms 914 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 1147 ms 919 ms 0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
7 1142 ms 929 ms POS7-0.BR2.LAX7.ALTER.NET [152.63.112.149]
8 37 ms 16 ms p64-5-0-1.r20.lsanca03.us.bb.gin.ntt.net [129.250.8.69]
9 19 ms 21 ms as-0.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.96]
10 1157 ms 951 ms po-4.r03.snjsca04.us.bb.gin.ntt.net [129.250.4.78]
11 1159 ms 945 ms a96-6-236-79.deploy.akamaitechnologies.com [96.6.236.79]
Ping statistics for www.verizon.net
Packets: Sent = 2, Received = 2, Lost = 0 (0.0%)
Round Trip Times: Minimum = 945ms, Maximum = 1159ms, Average = 1052ms
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
btw, if Verizon FIOS support asks you to do a speed test by going to http://speedtest.verizon.net, it'll probably show pretty good download and upload speed.
I did a traceroute to www2.verizon.net which hosts the speedtest app and sure enough it doesn't go thru the ....LSANCA-LCR-12.verizon-gni.net troubled router/device so that test is no good.
my trace to google.... it's pretty bad...
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.