- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
from chino hills again... getting slower as the night goes on...
Target Name: www.hulu.com
IP: 65.200.11.147
Date/Time: 10/28/2009 9:58:04 PM
1 0 ms Wireless_Broadband_Router.home [192.168.1.1]
2 3 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 555 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 554 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 553 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 556 ms 0.so-7-1-0.XL4.LAX15.ALTER.NET [152.63.1.242]
7 16 ms TenGigE0-7-1-0.GW4.LAX15.ALTER.NET [152.63.114.225]
8 564 ms a65.200.11.147.deploy.akamaitechnologies.com [65.200.11.147]
Ping statistics for www.hulu.com
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 564ms, Maximum = 564ms, Average = 564ms
Target Name: www.google.com
IP: 74.125.19.103
Date/Time: 10/28/2009 10:03:27 PM
1 0 ms Wireless_Broadband_Router.home [192.168.1.1]
2 3 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 527 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 534 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 544 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 16 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
7 551 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
8 25 ms ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.52]
9 28 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10 551 ms ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]
11 14 ms ae-1-69.edge1.SanJose1.Level3.net [4.68.18.14]
12 12 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
13 18 ms [209.85.251.98]
14 558 ms nuq04s01-in-f103.1e100.net [74.125.19.103]
Ping statistics for www.google.com
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 558ms, Maximum = 558ms, Average = 558ms
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
used to be able to watch apple.com HD trailers with no problems.. these days, i have to let it download first or else, it's constantly pausing. it's like having DSL connection but paying FIOS rates.. this is not right at all... it's been 2 weeks now.
Target Name: apple.com
IP: 17.112.152.57
Date/Time: 10/28/2009 10:19:44 PM
1 0 ms Wireless_Broadband_Router.home [192.168.1.1]
2 2 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 509 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 509 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 509 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 4 ms 0.ge-7-1-0.BR2.LAX15.ALTER.NET [152.63.116.161]
7 5 ms [192.205.35.161]
8 15 ms cr1.la2ca.ip.att.net [12.123.30.6]
9 14 ms cr1.sffca.ip.att.net [12.122.3.121]
10 517 ms cr1.sc1ca.ip.att.net [12.122.30.121]
11 13 ms gar2.sc1ca.ip.att.net [12.123.155.9]
12 15 ms [12.116.180.6]
13 17 ms [17.112.254.24]
14 14 ms [17.112.254.29]
15 522 ms apple.com [17.112.152.57]
Ping statistics for apple.com
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 522ms, Maximum = 522ms, Average = 522ms
Target Name: www.verizon.com
IP: 65.200.11.147
Date/Time: 10/28/2009 10:20:23 PM
1 0 ms Wireless_Broadband_Router.home [192.168.1.1]
2 12 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 514 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 513 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 511 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 521 ms 0.so-7-1-0.XL4.LAX15.ALTER.NET [152.63.1.242]
7 8 ms TenGigE0-7-1-0.GW4.LAX15.ALTER.NET [152.63.114.225]
8 525 ms a65.200.11.147.deploy.akamaitechnologies.com [65.200.11.147]
Ping statistics for www.verizon.com
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 525ms, Maximum = 525ms, Average = 525ms
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm getting poor results as well. Thought it was just me. Used pingtest.net. Tech support told us we just have an old computer. Never had this problem when I had cable from Time Warner.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12:00am, latest tracert to google.com
Tracing route to google.com [74.125.45.100]
over a maximum of 30 hops:
1 4 ms 6 ms 15 ms L300.LSANCA-VFTTP-142.verizon-gni.net [private]
2 667 ms 614 ms 613 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
3 636 ms 614 ms 613 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
4 636 ms 499 ms 523 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
5 546 ms 511 ms 614 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
6 7 ms 6 ms 5 ms 192.205.35.161
7 62 ms 61 ms 66 ms cr2.la2ca.ip.att.net [12.123.30.134]
8 63 ms 61 ms 61 ms cr2.dlstx.ip.att.net [12.122.28.177]
9 665 ms 716 ms 716 ms cr1.attga.ip.att.net [12.122.28.173]
10 666 ms 716 ms 717 ms 12.123.22.5
11 842 ms 707 ms 714 ms 12.88.97.6
12 635 ms 613 ms 614 ms 72.14.233.54
13 63 ms 75 ms 189 ms 72.14.232.213
14 68 ms 655 ms 716 ms 209.85.253.145
15 684 ms 761 ms 674 ms yx-in-f100.1e100.net [74.125.45.100]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nope not fixed
Taken exactly at midnight
Tracing route to www.l.google.com [74.125.19.99]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms myrouter.home [192.168.1.1]
2 5 ms 5 ms 4 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53
.1]
3 505 ms 511 ms 507 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 515 ms 544 ms 521 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 567 ms 594 ms 593 ms 0.so-1-2-0.XL4.LAX15.ALTER.NET [152.63.10.125]
6 8 ms 9 ms 8 ms 0.ge-6-1-0.BR2.LAX15.ALTER.NET [152.63.116.153]
7 576 ms 579 ms 569 ms xe-10-1-0.edge1.LosAngeles9.Level3.net [4.68.63.129]
8 10 ms 17 ms 17 ms ae-93-90.ebr3.LosAngeles1.Level3.net [4.69.144.244]
9 16 ms 17 ms 17 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
10 631 ms 626 ms 573 ms ae-83-83.csw3.SanJose1.Level3.net [4.69.134.234]
11 643 ms 668 ms 640 ms ae-3-89.edge1.SanJose1.Level3.net [4.68.18.142]
12 675 ms 681 ms 703 ms GOOGLE-INC.edge1.SanJose1.Level3.net [4.79.43.146]
13 678 ms 631 ms 622 ms 209.85.251.98
14 549 ms 517 ms 558 ms nuq04s01-in-f99.1e100.net [74.125.19.99]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks everyone, I just let them know & waiting on a response! Brett