- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FIOS support number is 888-553-1555.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Keep an eye on it tonight, and post traceroutes back. I will keep following up with it. Thanks Brett
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You have a time out...that is not good....
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.