1 edit | reply to Vamp
Re: [Northeast] High pings / bad routing...I got a new route by releasing my DHCP lease on the router and shutting it off. This is my traceroute now compared to earlier:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Kenneth>tracert 108.61.46.50
Tracing route to 108.61.46.50.choopa.net [108.61.46.50]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 4 ms 4 ms L100.SYRCNY-VFTTP-06.verizon-gni.net [72.90.76.1
]
3 4 ms 5 ms 4 ms G5-0-2-216.SYRCNY-LCR-02.verizon-gni.net [130.81
.179.122]
4 85 ms 91 ms 12 ms P15-3.CLPPVA-LCR-02.verizon-gni.net [130.81.28.1
86]
5 35 ms 33 ms 12 ms 0.xe-9-1-0.BR1.NYC1.ALTER.NET [152.63.4.241]
6 13 ms 12 ms 13 ms ae11.edge2.NewYork.Level3.net [4.68.62.41]
7 13 ms 13 ms 13 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8 13 ms 13 ms 13 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
9 16 ms 16 ms 16 ms ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]
10 12 ms 83 ms 33 ms ae-1-60.edge3.NewYork1.Level3.net [4.69.155.17]
11 20 ms 24 ms 24 ms CHOOPA-LLC.edge3.NewYork1.Level3.net [4.31.21.58
]
12 19 ms 18 ms 19 ms ve67-br1.pnj1.choopa.net [108.61.93.109]
13 14 ms 14 ms 14 ms 108.61.92.162.choopa.net [108.61.92.162]
14 17 ms 17 ms 14 ms 108.61.46.50.choopa.net [108.61.46.50]
Trace complete.
C:\Users\Kenneth>
|
|
jk111
join:2013-01-27
Auburn, NY | reply to Vamp
Let me know how the rest of today goes in terms of latency and trace routes, Saturdays are probably good days to test it. |
|
 Vamp5c077Premium
join:2003-01-28
MD
kudos:1 | said by jk111:Let me know how the rest of today goes in terms of latency and trace routes, Saturdays are probably good days to test it.
It was fine the last couple weekdays, no night time change.
--
75/35 FIOS || MSN Msgr: scott001^gmail_com |
|
| reply to Vamp
I have pretty bad routing to alter.net today myself. Ping's fine other places.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
quote:
C:\Users\Jcink>ping youtube.com
Pinging youtube.com [173.194.43.46] with 32 bytes of data:
Reply from 173.194.43.46: bytes=32 time=12ms TTL=251
Reply from 173.194.43.46: bytes=32 time=17ms TTL=250
Ping statistics for 173.194.43.46:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 17ms, Average = 14ms
Control-C
^C
C:\Users\Jcink>tracert 69.197.24.136 -t
Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
[-R] [-S srcaddr] [-4] [-6] target_name
Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list (IPv4-only).
-w timeout Wait timeout milliseconds for each reply.
-R Trace round-trip path (IPv6-only).
-S srcaddr Source address to use (IPv6-only).
-4 Force using IPv4.
-6 Force using IPv6.
C:\Users\Jcink>tracert jcink.com
Tracing route to jcink.com [69.197.24.136]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.2.1
2 1 ms 1 ms 3 ms 192.168.0.1
3 6 ms 7 ms 13 ms L300.NWRKNJ-VFTTP-90.verizon-gni.net [96.242.25.
1]
4 19 ms 16 ms 8 ms G0-14-0-4.NWRKNJ-LCR-22.verizon-gni.net [130.81.
187.150]
5 63 ms 26 ms 51 ms so-4-0-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.
22.64]
6 19 ms 14 ms 12 ms xe-6-1-3-0.NY325-BB-RTR2.verizon-gni.net [130.81
.23.234]
7 29 ms 15 ms 14 ms 0.so-6-0-3.XT2.NYC4.ALTER.NET [152.63.10.25]
8 16 ms 17 ms 15 ms TenGigE0-5-4-0.GW8.NYC4.ALTER.NET [152.63.18.206
]
9 105 ms 105 ms 104 ms tinet-gw.customer.alter.net [152.179.72.122]
10 194 ms 197 ms 198 ms xe-2-0-0.lax30.ip4.tinet.net [89.149.181.165]
11 * * * Request timed out.
12 197 ms 200 ms 197 ms . [69.197.1.190]
13 227 ms 223 ms 225 ms ddos-shield.jcink.com [69.197.24.136]
Trace complete.
C:\Users\Jcink>
|
|
1 edit | reply to Vamp
Everything is still fine for me after getting a new route to the server. I still get routed to Culpeper, VA for some reason but now I am not going through that router/gateway that was causing ping issues for me.
I hope that Verizon still looks into this and resolves the issues with their router and routing.
Apparently VZ_Support was online around 3 hours ago. No response to my pm or a reply to my thread though.  |
|
| reply to Vamp
It's back again. Seriously Verizon, fix your crappy routing/routers. |
|
1 edit | reply to Vamp
Edit: Nevermind. Misread the trace route. It is indeed still spiking within the Verizon network. :/
Not spiking as bad as before though. Ping will spike up briefly for a bit and go back down. This still needs to be sorted out though as I should be seeing much lower ping to local servers. |
|
 RolteC0h
join:2001-05-20
Fresh Meadows, NY
kudos:1 | reply to Vamp
I am pretty sure that it is safe to say: no one from Verizon will agree to bad routing within Verizon nor will anyone every respond to those types of posts in the direct forum. I haven't seen that before, so it probably won't change. I also do not expect a direct response to anything you ask of any current Verizon employee. Its not allowed/they are not going to risk their jobs.
But to show something weird. I am seeing horrific ping times to almost everything - but NOT all at the exact same times tonight.
Here is a tracert to myself from a road runner connection, and at the exact same time, a tracert back to the road runner connection. Very weird results:
Tracing route to cpe-142-255.nyc.res.rr.com [142.255.]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [192.168.1.1]
2 4 ms 1 ms 1 ms L.NYCMNY-VFTTP.verizon-gni.net [71
3 8 ms 8 ms 7 ms G0-1-1-3.NYCMNY-LCR-22.verizon-gni.net [130.81.188.72]
4 5 ms 6 ms 6 ms so-6-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.151.224]
5 6 ms 6 ms 7 ms 0.xe-9-1-0.BR2.NYC4.ALTER.NET [152.63.23.141]
6 * * * Request timed out.
7 7 ms * * Vlan2135.icore2.NTO-NewYork.as6453.net [216.6.81.37]
8 92 ms 95 ms 99 ms Vlan576.icore2.NTO-NewYork.as6453.net [209.58.26.34]
9 33 ms 30 ms 31 ms 107.14.19.146
10 20 ms 23 ms 22 ms 107.14.19.23
11 45 ms 47 ms * bun6-nyquny91-rtr001.nyc.rr.com [24.29.148.253]
12 104 ms 103 ms 106 ms bun110.nycmnyl-rtr01.nyc.rr.com [184.152.112.76]
13 120 ms 115 ms * tenge18-10-nycmnyl-c404.nyc.rr.com [24.168.134.222]
14 106 ms 107 ms 120 ms cpe-142-255-.nyc.res.rr.com [142.255.]
Trace complete.
Tracing route to [100.]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Router [192.168.1.1]
2 34 ms 27 ms 28 ms cpe-142-255-0-1.nyc.res.rr.com [142.255.0.1]
3 29 ms 12 ms 11 ms tenge-0-2-0-3-nycmnyl-rtr2.nyc.rr.com [24.168.134.221]
4 16 ms 15 ms 15 ms bun110.nycmnytg-rtr001.nyc.rr.com [184.152.112.129]
5 * 17 ms 16 ms bun6-nycmnytg-rtr002.nyc.rr.com [24.29.148.250]
6 21 ms 13 ms 15 ms ae-4-0.cr0.nyc30.tbone.rr.com [66.109.6.78]
7 12 ms 15 ms 11 ms 107.14.19.153
8 22 ms 22 ms 19 ms 216.55.0.65
9 32 ms 23 ms 31 ms ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
10 31 ms 23 ms 36 ms vb1010.rar3.nyc-ny.us.xo.net [216.156.0.17]
11 18 ms 21 ms 35 ms 207.88.14.178.ptr.us.xo.net [207.88.14.178]
12 34 ms 34 ms 34 ms 206.111.13.126.ptr.us.xo.net [206.111.13.126]
13 * 110 ms 113 ms 0.xe-1-1-2.NY325-BB-RTR2.verizon-gni.NET [152.63.20.214]
14 * * * Request timed out.
15 116 ms 136 ms 123 ms pool-100nycmny.fios.verizon.net [100]
Trace complete.
|
|
| reply to Vamp
That's ridiculous. They really need to look into it or they risk losing customers. The proof is there that it's within the Verizon network, either some router or poor routing decisions.
Any way to get them to take their heads out from their behinds to have someone that can do something look into it and resolve the issue? For an issue this widespread it's just bad business for them to continue ignoring complaints. I wouldn't mind so much if the spikes were short lived and were mild fluctuations but when it's spiking up to 80ms+ it is plainly unacceptable.
I'm not sure what good the direct sections are if they won't respond to such issues. I just don't fancy being kept on the phone for over an hour, run through the motions, a tech to come out only for them to realize it's not an issue on my end and deny any sort of responsibility with their network. When I first signed up for Fios I was on the phone for over an hour over something ridiculous, an incompetent representative kept claiming I couldn't sign up for internet service without bundling voice due to some unheard of law (to me) in New York. Never again.
--
My Website: »www.xtemu.com
My Speedtest: »www.speedtest.net/result/1218984197.png
|
|
| reply to Vamp
Maybe Verizon fixed the issue? Seeing low ping all around and no spikes today as of yet. |
|
| reply to Vamp
Well that's a big fat nope. Spikes around 7PM - 8PM EST. >_ |
|
| reply to Vamp
Well I have an installation appointment for TV this Thursday. I will be telling them to relay the message to Verizon to fix their damn network. |
|
| reply to Vamp
Anyone got anywhere with Verizon yet? Still no improvement on my end, severe lag spikes everyday later in the day. Even when my ping is lower I am lagging in the online game I play. |
|
1 edit | reply to Vamp
Delaware reporting in, see this issue too. It comes and goes with the hours, varies from the normal ~20ms up to ~120ms.
Same routes, distinctly different pings over hops 5-6 depending on the mood. Sure hope someone fixes it soon, scout is hard to play with 120ms ping.
~120ms route:
traceroute to 208.78.165.46 (208.78.165.46), 64 hops max, 72 byte packets
1 192.168.3.1 (192.168.3.1) 0.619 ms 0.366 ms 0.430 ms
2 l100.phlapa-vfttp-90.verizon-gni.net (71.244.110.1) 8.243 ms 9.050 ms 7.227 ms
3 g0-10-4-4.phlapa-lcr-22.verizon-gni.net (130.81.188.186) 12.755 ms 11.333 ms 13.222 ms
4 so-3-1-0-0.phil-bb-rtr2.verizon-gni.net (130.81.22.60) 11.971 ms 12.120 ms 12.737 ms
5 0.xe-4-1-0.br3.iad8.alter.net (152.63.33.21) 19.968 ms 17.358 ms 19.980 ms
6 63-235-40-49.dia.static.qwest.net (63.235.40.49) 131.893 ms 104.213 ms 103.161 ms
7 stn3-edge-01.inet.qwest.net (67.14.28.50) 112.676 ms 114.603 ms 115.393 ms
8 65.126.30.62 (65.126.30.62) 104.660 ms 106.904 ms 109.651 ms
9 208.78.167.3 (208.78.167.3) 100.145 ms 98.196 ms 100.175 ms
~20ms route:
traceroute to 208.78.165.46 (208.78.165.46), 64 hops max, 72 byte packets
1 192.168.3.1 (192.168.3.1) 0.761 ms 0.321 ms 0.511 ms
2 l100.phlapa-vfttp-90.verizon-gni.net (71.244.110.1) 6.489 ms 8.003 ms 7.007 ms
3 g0-10-4-4.phlapa-lcr-22.verizon-gni.net (130.81.188.186) 12.959 ms 11.354 ms 13.226 ms
4 so-3-1-0-0.phil-bb-rtr2.verizon-gni.net (130.81.22.60) 11.716 ms 12.681 ms 12.229 ms
5 0.xe-4-1-0.br3.iad8.alter.net (152.63.33.21) 20.263 ms 19.627 ms 19.989 ms
6 63-235-40-49.dia.static.qwest.net (63.235.40.49) 19.995 ms 19.632 ms 19.962 ms
7 stn3-edge-01.inet.qwest.net (67.14.28.50) 19.975 ms 19.625 ms 19.987 ms
8 65.126.30.62 (65.126.30.62) 42.713 ms 19.588 ms 20.213 ms
9 208.78.167.3 (208.78.167.3) 19.955 ms 21.647 ms 19.999 ms |
|
| reply to Vamp
ISOC Workshop Resource Centre (Eugene, Oregon, USA) | 
Indiana University | 
heise.de | 
l.root-servers.net |
In a few days I will post updated charts, I just added the ones that only go for 30 hours 3 days ago so the 10 day charts are mostly worthless on those so far. |
|
|
|
| reply to Vamp
For some reason, the last two days have been fine during the day. Suddenly after 8PM ping spikes up like everyone decides, "Hey let's all go online now", either that or Verizon's network is just derpy.
I wouldn't mind if the spikes were mild such as spikes up to 10ms - 15ms but it is spiking from sub 20ms ping up to 80ms+. |
|
| reply to Vamp
Like clockwork, after 8PM every night now. Talked to the tech today and he mentioned something about there being a fire somewhere and due to that customers were assigned another route, overloading whatever router/gateway everyone was switched to. |
|
jk111
join:2013-01-27
Auburn, NY | reply to Vamp
I tweeted to Verizon support tonight with links to this thread and one on Verizon.com forums. I will continue to do so every day until this issue is fixed. Worth a shot I guess.... |
|
| reply to Vamp
Same bull**** again tonight. High latency and slow browsing around 6PM instead of the usual 8PM it has been the past week. |
|
| reply to Vamp
Can't even load MyVerizon to pay my bill. Of course they don't care and won't hesitate to shut my service off if I can't pay my bill even if it's the fault of their network preventing me from doing so. |
|
