- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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/
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Chino HIlls, Ca area customers,
If you have not already opened a ticket with Verizon I would strongly recommend doing so. Its a utterly frustrating and difficult process that will not end up with them solving your problem. BUT, I'm hoping that with enough tickets from the same area with the same problem it might make someone at Verizon see that the issues is not a PC problem but a problem within the Verizon network.
I know I know....it's wishful thinking on my part but what else can we do...I mean really what else?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
trace route to 192.76.85.245 (verizon.com) seems to go thru the bad performing router but trace route to 63.110.246.35 (www.verizon.com) is much better. why can't everything be routed using G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net instead of the ... LCR-12.xxxx router junk.
$ tracert verizon.com
Tracing route to verizon.com [192.76.85.245]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 2 ms 3 ms 3 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 537 ms 522 ms 523 ms G4-0-6-1242.LSANCA-LCR-12.verizon-gni.net [130.81.140.162]
4 534 ms 533 ms 532 ms so-4-3-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.246]
5 526 ms 520 ms 547 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 549 ms 525 ms 522 ms 0.ge-7-0-0.XT2.SAC1.ALTER.NET [152.63.49.90]
7 487 ms 493 ms 482 ms GigabitEthernet7-0-0.GW9.SAC1.ALTER.NET [152.63.55.77]
8 492 ms 498 ms 469 ms verizon-gw.customer.alter.net [157.130.203.246]
9 487 ms 496 ms 517 ms 192.76.84.5
10 * * * Request timed out.
11 * *
$ tracert www.verizon.com
Tracing route to a1280.g.akamai.net [63.80.4.26]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 2 ms 3 ms 3 ms L100.LSANCA-VFTTP-142.verizon-gni.net [173.55.53.1]
3 5 ms 4 ms 5 ms G4-0-6-1142.LSANCA-LCR-11.verizon-gni.net [130.81.140.122]
4 5 ms 5 ms 5 ms so-4-3-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.244]
5 6 ms 6 ms 6 ms 0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
6 14 ms 13 ms 13 ms 0.ge-7-1-0.XL3.SJC7.ALTER.NET [152.63.48.254]
7 534 ms 516 ms 496 ms TenGigE0-6-2-0.GW3.SJC7.ALTER.NET [152.63.50.49]
8 14 ms 11 ms 13 ms 63.80.4.26
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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