hop in connection to game server from Tampa area in FL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
See my trace below from PingPlotter. It shows a bad connection at hop 6 to teliasonera. I talked to a few friends that have helped me along this far, but they don't know how to resolve a bad hop. This has been happening for almost a week now to a server in Chicago. Destination ip is 50.31.112.213. Anyone have any clues on how to begin to fix the hop so that I can maintain a better ping on this game server? Thanks in advance for your help.
Target Name: chi.lowpinggameservers.com
IP: 50.31.112.213
Date/Time: 8/1/2015 5:47:59 PM to 8/1/2015 5:52:58 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 120 57 47.5 1 7 1 Wireless_Broadband_Router.home [192.168.1.1]
2 120 57 47.5 4 76 12 L100.TAMPFL-VFTTP-40.verizon-gni.net [96.252.135.1]
3 120 58 48.3 8 38 16 G0-5-3-5.TAMPFL-LCR-22.verizon-gni.net [130.81.60.146]
4 119 119 100.0 0 0 0 [-]
5 120 57 47.5 14 33 19 0.ae12.GW1.MIA19.ALTER.NET [140.222.225.79]
6 120 57 47.5 146 165 155 teliasonera-gw.customer.alter.net [152.179.236.22]
7 120 57 47.5 155 188 165 atl-bb1-link.telia.net [62.115.141.157]
8 120 57 47.5 173 197 183 chi-b21-link.telia.net [62.115.143.60]
9 120 58 48.3 180 207 192 giglinx-ic-310968-chi-b21.c.telia.net [62.115.51.194]
10 120 56 46.7 180 364 197 te8-7.dist02.chi18.steadfast.net [208.100.32.59]
11 120 57 47.5 180 227 193 chi.lowpinggameservers.com [50.31.112.213]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you download this tool:
And let that run for awhile, and take a screenshot of it so it shows up nicely and easy to read?
Example:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sure I downloaded it and I will run it for a bit. It seems to be very similar information to what I posted that it's gathering.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I live in the tampa bay area, and Im getting the same exact problem with other gaming servers. If you find out how to fix it please update me, I went from getiing 40ms to a Newyork server to over 120
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Will do if I hear anything. I've heard from a fellow gamer that possibly going through a VPN will help. I haven't signed up for one yet, but i'm seriously considering it. Some of them you pay monthly or yearly which makes it substantially cheaper. I've tried VPN before for international purposes, but never for something like this. I'm not sure if it will work or not. If I try it, I will let you know how it goes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
same problem here:
Tracing route to 167.114.42.236 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1]
2 5 ms 4 ms 3 ms L100.TAMPFL-VFTTP-144.verizon-gni.net [96.254.179.1]
3 5 ms 7 ms 9 ms G0-9-3-7.TAMPFL-LCR-21.verizon-gni.net [130.81.138.162]
4 * * * Request timed out.
5 14 ms 16 ms 14 ms 0.ae11.GW1.MIA19.ALTER.NET [140.222.225.77]
6 187 ms 189 ms 189 ms teliasonera-gw.customer.alter.net [152.179.236.22]
7 201 ms 203 ms 208 ms ash-bb3-link.telia.net [62.115.141.74]
8 212 ms 214 ms 211 ms nyk-bb1-link.telia.net [213.155.134.148]
9 216 ms 213 ms 211 ms nyk-b2-link.telia.net [213.155.130.28]
10 249 ms 245 ms 245 ms nwk-1-6k.nj.us [178.32.135.212]
11 262 ms 253 ms 251 ms bhs-g1-a9.qc.ca [198.27.73.205]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is nothing to fix. That particular router(or hop) is just not returning the ping reply. It is a security feature that is sometimes utilized.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Inigo31 wrote:
There is nothing to fix. That particular router(or hop) is just not returning the ping reply. It is a security feature that is sometimes utilized.
There is something that has to be fixed - that is the interconnection between Verizon and Telia. It's nothing users/customers can really fix though. There is no reason, even with ICMP de-prioritization, that a route should be showing >100ms pings within the United States throughout a trace.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
this is terrible. i can't even stay in the game server long enough to even do anything. it's dropping connection constantly and my ping spikes between 50-1000 and higher, and dropping packets nonstop.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you aware of how to fix it? I'm about to write TeliaSonera an email to complain, but another person that i play with is having the same issues on the same router. He said that if it was more than 3 hops away, Verizon basically said it's not their problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yeah this is getting stupid. Ive had the same problem for the past few weeks and verizon says they cant do anything, even though people with different providers arent having this problem.
Tracing route to hcteams.com [72.20.56.226]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1
.1]
2 6 ms 5 ms 4 ms L100.TAMPFL-VFTTP-146.verizon-gni.net [173.65.12
.1]
3 12 ms 11 ms 10 ms G0-9-3-3.TAMPFL-LCR-22.verizon-gni.net [130.81.1
40.84]
4 * * * Request timed out.
5 16 ms 15 ms 15 ms 0.ae10.GW1.MIA19.ALTER.NET [140.222.231.83]
6 261 ms 258 ms 260 ms teliasonera-gw.customer.alter.net [152.179.236.2
2]
7 290 ms 297 ms 300 ms ash-bb3-link.telia.net [62.115.141.74]
8 300 ms 297 ms 301 ms nyk-bb1-link.telia.net [62.115.138.24]
9 298 ms 299 ms 298 ms nyk-b5-link.telia.net [213.155.130.247]
10 295 ms 294 ms 294 ms pni-as1299-nyc1.staminus.net [69.197.1.78]
11 * * * Request timed out.
12 319 ms 314 ms 315 ms . [72.20.56.226]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
https://www.youtube.com/watch?v=c24ex7KYcPA
Here's a video of what this terrible hop is doing to online gaming
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After 2 calls this week, and a tech over the web who actually RESET my machine because I wouldn't budge (you know....SIR, there IS a problem here! "no there isn't, maybe it's your computer, the game, blah blah blah..") they just sent me a new router. Yea, because I'm sure THAT is the problem.
So when I get the new router tomorrow, verizon's MAGIC FIX, I expect my problems to stop.
...and when they don't, I'll be on the phone again, trying to chew my way up the chain to talk to the person who will hear what I have to say as I cancel my service.
DO YOU HEAR US, VERIZON?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No Verizon doesn't hear you as this is peer to peer.
There doesn't appear to be anything wrong in the Tampa area, however it looks like there is something wrong with teliasonera-gw.customer.alter.net which is a Verizon server. The big increase in response time occurs between it and another alter.net server and then remains bad to the end of the trace.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So if this is "peer to peer," yet one of the "peers" they are sending our data through is a Verizon server...and that hop is the cause of the problem.....what is the endgame here? Does VZ just throw up their hands and say "not our problem!" ?
Is the problem likely to get fixed? Because if it isn't, I can't afford to pay for internet I can't use. Netflix cutting in and out, and pings circa 1993 with a double phone modem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The forums are peer to peer. Only a few Verizon admins are regulars here. And they have very limited capabilities to help you other to occassionally escalte a already open problem. Even then this is not likely to be of those types. All the verizon admins have a verizon tag attached. the CL attached to mine and a few others is not because we work for Verizon. Myself I'm a retired systems programmer from another industry entirely.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Routing is still terrible, 350-450ms. It seems to be getting worse to different destinations every day
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tracing route to WIN-TGPS0LQCFCC [94.23.145.197]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 4 ms 4 ms L100.TAMPFL-VFTTP-144.verizon-gni.net [96.254.17
9.1]
3 7 ms 12 ms 12 ms G0-9-3-7.TAMPFL-LCR-22.verizon-gni.net [130.81.1
40.80]
4 * * * Request timed out.
5 13 ms 14 ms 14 ms 0.ae12.GW1.MIA19.ALTER.NET [140.222.225.79]
6 310 ms 307 ms 312 ms teliasonera-gw.customer.alter.net [152.179.236.2
2]
7 338 ms 339 ms 337 ms ash-bb3-link.telia.net [62.115.141.117]
8 * 339 ms 339 ms nyk-bb1-link.telia.net [62.115.136.202]
9 342 ms 342 ms * nyk-b2-link.telia.net [62.115.112.107]
10 338 ms 342 ms 344 ms nwk-1-a9.nj.us [178.32.135.212]
11 413 ms 409 ms 414 ms ldn-1-a9.uk.eu [178.32.135.79]
12 414 ms 414 ms 412 ms rbx-g1-a9.fr.eu [91.121.128.86]
13 412 ms 417 ms 412 ms rbx1-3a-a9.fr.eu [37.187.231.100]
14 415 ms 414 ms 414 ms WIN-TGPS0LQCFCC [94.23.145.197]
15 413 ms 416 ms 414 ms WIN-TGPS0LQCFCC [94.23.145.197]
Trace complete.
this is unacceptable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Problem is fixed! (At least on my end). Contacted support and they escalated the issue and I'm back down to normal pings. It's not as good as it used to be (135-140ms to this one particular server, up from 105-110ms), but infinitely better than 350-450ms. I suppose the 25-30ms increase is due to an extra hop going from Tampa to Miami, then to atlanta, instead of from Tampa, to Atlanta
