| Constant bad latency/pings to game server I am experiencing some pretty bad latency/ping on a game server for the past week or so. This game server is located in Virginia, which is just 4 states below me. I get better pings and stuff from servers halfway across the world (typically 85-95ms to servers in Europe, across a damn ocean.)
Tracing route to badrush.info [64.34.181.15]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 3 ms 5 ms 10.20.9.2
3 7 ms 6 ms 5 ms 64.222.166.108
4 15 ms 15 ms 15 ms burl-lnk-70-109-168-138.ngn.east.myfairpoint.net [70.109.168.138]
5 14 ms 16 ms 13 ms pool-64-222-213-130.port.east.myfairpoint.net [64.222.213.130]
6 17 ms 17 ms 18 ms xe-1-2-0.mpr4.bos2.us.above.net [64.125.71.169]
7 22 ms 42 ms 32 ms xe-0-0-0.mpr3.bos2.us.above.net [64.125.25.61]
8 59 ms 57 ms 28 ms xe-4-3-0.cr1.lga5.us.above.net [64.125.24.106]
9 45 ms 45 ms 43 ms xe-3-2-0.cr1.ord2.us.above.net [64.125.24.34]
10 100 ms 99 ms 99 ms xe-1-2-0.cr1.sjc2.us.above.net [64.125.26.229]
11 124 ms 99 ms 99 ms xe-7-0-0.mpr3.sjc7.us.above.net [64.125.24.2]
12 104 ms 105 ms 105 ms Equinix-SJO.Peer1.net [206.223.116.30]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
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 104 ms 104 ms 104 ms badrush.info [64.34.181.15] |
|
 tschmidtPremium,MVM
join:2000-11-12
Milford, NH
kudos:8
 ·G4 Communications
·Fairpoint Commun..
 ·Hollis Hosting
| This does not appear to be a FairPoint problem but a problem with the transit provider Above.net. Notice hop 6 the first non-FP hop looks fine. The problem is occurring within the above.net network at hops 7/8/9/10. Notice that latency is varying a lot starting at hop 7. Probably an indication of network congestion as earlier hops are very stable.
Looks like above.net got sold last year.
»www.zayo.com/abovenet
»en.wikipedia.org/wiki/Zayo_Group
You might try calling FairPoint and let them know there seems to be a problem with above.net/Zayo group transit carrier but I would not hold my breath.
Good Luck
/Tom |
|
amh1
join:2013-01-07
Salem, NH | reply to Anon5
Have been delaying (procrastinating) trying G4, but I think FP is pushing me to do it.
They are up to their usual once every few months screw something up routine.
Upload speeds are ~0.1Mbps (downloads ~1-2Mb) on a 3Mb/768kb setup.
Pings to Boston speedtest.net server average ~550ms (badrush.info and google.com tracerouts shown below)
Reported problem, ticket opened but I think I am done with FP
--- Trace Route Test Results --- (badrush)
1 10.20.15.1 (10.20.15.1) 7.635 ms 7.574 ms 7.150 ms
2 64.222.166.237 (64.222.166.237) 593.670 ms * 620.334 ms
3 pool-64-222-213-132.port.east.myfairpoint.net (64.222.213.132) 594.568 ms 579.512 ms 573.274 ms
4 xe-1-2-0.mpr4.bos2.us.above.net (64.125.71.169) 594.915 ms 610.290 ms 602.133 ms
5 xe-0-0-0.mpr3.bos2.us.above.net (64.125.25.61) 648.932 ms 593.927 ms 627.965 ms
6 xe-3-3-0.cr1.lga5.us.above.net (64.125.25.42) 602.059 ms 657.852 ms 587.118 ms
7 xe-3-3-0.cr1.ord2.us.above.net (64.125.24.38) 611.411 ms 627.049 ms 612.897 ms
8 xe-5-3-0.cr1.sjc2.us.above.net (64.125.26.13) 685.518 ms 669.680 ms 671.085 ms
9 xe-7-0-0.mpr3.sjc7.us.above.net (64.125.24.2) 686.112 ms 684.657 ms 703.059 ms
10 Equinix-SJO.Peer1.net (206.223.116.30) 677.991 ms 669.122 ms 673.492 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 badrush.info (64.34.181.15) 680.288 ms 676.270 ms 662.618 ms
--- Trace Route Test Results ---(google)
1 10.20.15.1 (10.20.15.1) 7.589 ms 7.510 ms 7.183 ms
2 64.222.166.237 (64.222.166.237) 575.999 ms * 567.505 ms
3 pool-64-222-213-132.port.east.myfairpoint.net (64.222.213.132) 592.954 ms 585.433 ms 663.419 ms
4 xe-3-2-0.mpr4.bos2.us.above.net (208.184.223.233) 575.735 ms 572.791 ms 569.327 ms
5 xe-0-0-0.mpr3.bos2.us.above.net (64.125.25.61) 571.280 ms 562.832 ms 572.317 ms
6 xe-5-3-0.cr1.lga5.us.above.net (64.125.24.110) 584.075 ms 609.994 ms 573.549 ms
7 xe-1-0-0.cr2.lga5.us.above.net (64.125.29.46) 603.788 ms 780.361 ms 661.834 ms
8 * xe-1-0-1.er4.lga5.us.above.net (64.125.24.173) 609.079 ms 570.573 ms
9 72.14.212.130 (72.14.212.130) 586.535 ms * 613.841 ms
10 209.85.248.178 (209.85.248.178) 589.291 ms 587.498 ms 616.877 ms
11 72.14.239.250 (72.14.239.250) 585.781 ms 580.411 ms 604.748 ms
12 lga15s28-in-f8.1e100.net (74.125.226.200) 599.071 ms 590.973 ms 581.178 ms
Fairpoint DSL internet service is not reliable enough for me. |
|
| reply to tschmidt
said by tschmidt:This does not appear to be a FairPoint problem but a problem with the transit provider Above.net. Notice hop 6 the first non-FP hop looks fine. The problem is occurring within the above.net network at hops 7/8/9/10. Notice that latency is varying a lot starting at hop 7. Probably an indication of network congestion as earlier hops are very stable.
Looks like above.net got sold last year.
»www.zayo.com/abovenet
»en.wikipedia.org/wiki/Zayo_Group
You might try calling FairPoint and let them know there seems to be a problem with above.net/Zayo group transit carrier but I would not hold my breath.
Good Luck
/Tom
They must have broke something then, since it's been an issue for over a week now with the pings to that server reaching over 600ms. I haven't been able to play reliably at any time of day, since whether it's 8AM, 12PM, 4PM, 8PM or 12AM...pings are still incredibly high 24/7. |
|
| reply to tschmidt
said by tschmidt:This does not appear to be a FairPoint problem but a problem with the transit provider Above.net. Notice hop 6 the first non-FP hop looks fine. The problem is occurring within the above.net network at hops 7/8/9/10. Notice that latency is varying a lot starting at hop 7. Probably an indication of network congestion as earlier hops are very stable.
Looks like above.net got sold last year.
»www.zayo.com/abovenet
»en.wikipedia.org/wiki/Zayo_Group
You might try calling FairPoint and let them know there seems to be a problem with above.net/Zayo group transit carrier but I would not hold my breath.
Good Luck
/Tom
I'm also not exactly sure why I am being routed all the way to San Jose, California, when the server in question is located in Virginia which is only a few states away from me. |
|
amh1
join:2013-01-07
Salem, NH | Anon5,
Aside from badrush.info, what are your ping latencies and upload/download speeds like?
After complaining and getting the service ticket open, magically next day my latencies went back to normal and bandwidths are ok (especially upload, which seemed to cause all the probs).
It does appear that FP was having some issues last few days on their side, at least for me. |
|
| said by amh1:Anon5,
Aside from badrush.info, what are your ping latencies and upload/download speeds like?
After complaining and getting the service ticket open, magically next day my latencies went back to normal and bandwidths are ok (especially upload, which seemed to cause all the probs).
It does appear that FP was having some issues last few days on their side, at least for me.
All ping/latencies normal. All speed tests are normal. Note this is fiber optic "FAST" and not FP DSL.
Speedtest:
|
|
tschmidtPremium,MVM
join:2000-11-12
Milford, NH
kudos:8 Reviews:
·G4 Communications
·Fairpoint Commun..
·Hollis Hosting
| said by Anon5 : All ping/latencies normal. All speed tests are normal. Note this is fiber optic "FAST" and not FP DSL.
Great, now that things are working again capture another traceroute to use as a reference if service deteriorates.
How did you determine routing was through West coast? I would not place too much faith in server names if that is what you were using. However if we assume SJC2 is really San Jose CA could be the result of congestion elsewhere in the network. Remember, routing is dynamic so routers make packet by packet decisions as to how best to forward packets.
/tom
|
|
| said by tschmidt:said by Anon5 : All ping/latencies normal. All speed tests are normal. Note this is fiber optic "FAST" and not FP DSL.
Great, now that things are working again capture another traceroute to use as a reference if service deteriorates. How did you determine routing was through West coast? I would not place too much faith in server names if that is what you were using. However if we assume SJC2 is really San Jose CA could be the result of congestion elsewhere in the network. Remember, routing is dynamic so routers make packet by packet decisions as to how best to forward packets. /tom You didn't read. He asked me if everything was normal outside of the server I was trying to go on, I replied yes. Problem is still an issue hitting badrush.info.
Also as far as the routing goes, they have the abbreviation of the city as part of the hostmask name. Also I can lookup the IP address on the hops and find the location. of that IP.
Here is another tracert to badrush.info showing good routing, but right after Washington DC it shoots off to Los Angeles and San Jose:
Tracing route to badrush.info [64.34.181.15]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 6 ms 5 ms 8 ms 10.20.9.2
3 6 ms 8 ms 8 ms 64.222.166.108
4 15 ms 14 ms 15 ms burl-lnk-70-109-168-138.ngn.east.myfairpoint.net [70.109.168.138]
5 13 ms 15 ms 14 ms pool-64-222-213-130.port.east.myfairpoint.net [64.222.213.130]
6 16 ms 17 ms 17 ms xe-1-2-0.mpr4.bos2.us.above.net [64.125.71.169]
7 26 ms 28 ms 27 ms xe-4-2-0.cr2.dca2.us.above.net [64.125.29.34]
8 54 ms 55 ms 55 ms xe-0-2-0.cr2.iah1.us.above.net [64.125.28.50]
9 87 ms 87 ms 88 ms xe-0-3-0.cr2.lax112.us.above.net [64.125.30.50]
10 86 ms 87 ms 89 ms xe-1-0-0.cr1.lax112.us.above.net [64.125.30.237]
11 121 ms 92 ms 98 ms xe-0-2-0.cr1.sjc2.us.above.net [64.125.26.26]
12 94 ms 95 ms 95 ms xe-7-0-0.mpr3.sjc7.us.above.net [64.125.24.2]
13 95 ms 98 ms 97 ms Equinix-SJO.Peer1.net [206.223.116.30]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
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 * * * Request timed out.
24 105 ms 107 ms 105 ms badrush.info [64.34.181.15]
Hop #9 xe-0-3-0.cr2.lax112.us.above.net [64.125.30.50]
IP Address
64.125.30.50
Country Code State/Region
US CALIFORNIA
City Postal Code
LOS ANGELES 90001
ISP Time Zone
ABOVENET COMMUNICATIONS INC -07:00
Latitude Longitude
34.052230834961 -118.24368286133
Hop #11 xe-0-2-0.cr1.sjc2.us.above.net [64.125.26.26]
IP Address
64.125.26.26
Country Code State/Region
US CALIFORNIA
City Postal Code
SAN JOSE 95101
ISP Time Zone
ABOVENET COMMUNICATIONS INC -07:00
Latitude Longitude
37.339389801025 -121.89495849609 |
|
| Correction on my last post. Not Washington DC, that was for another issue I had.
7 26 ms 28 ms 27 ms xe-4-2-0.cr2.dca2.us.above.net [64.125.29.34]
This is Arlington, Virginia. Virginia is where badrush.info server is located.
The next hop #8 shoots me off to Houston, Texas and then to Los Angeles and then San Jose.
I don't know why I'm being routed off to Texas, LA and San Jose AFTER the hop that jumps into the state where the server I'm trying to play on is located. It makes no god damn sense. |
|
|
|
 NormanSI gave her time to steal my mind awayPremium,MVM
join:2001-02-14
San Jose, CA
kudos:9 | said by Anon5 :I don't know why I'm being routed off to Texas, LA and San Jose AFTER the hop that jumps into the state where the server I'm trying to play on is located. It makes no god damn sense.
But do note that this odd route happens on Above.net transit, which is outside of Frontier control. Frontier hands you of to Above.net on the East Coast.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
| I never thought I would ever say this about Cogentco, but thank you Cogentco for saving me from the horrible Above.net routing!
I can FINALLY play on the game server now.
Tracing route to badrush.info [64.34.181.15]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 5 ms 4 ms 4 ms 10.20.9.2
3 6 ms 4 ms 6 ms 64.222.166.108
4 14 ms 15 ms 14 ms burl-lnk-70-109-168-138.ngn.east.myfairpoint.net
[70.109.168.138]
5 23 ms 25 ms 25 ms te7-5.ccr01.alb02.atlas.cogentco.com [38.104.52.
21]
6 24 ms 24 ms 21 ms te8-1.ccr01.jfk01.atlas.cogentco.com [154.54.5.3
7]
7 21 ms 21 ms 21 ms te0-3-0-7.ccr21.jfk02.atlas.cogentco.com [154.54
.7.69]
8 23 ms 26 ms 21 ms te0-2-0-3.ccr21.jfk07.atlas.cogentco.com [154.54
.83.162]
9 20 ms 19 ms 19 ms tiscali.jfk07.atlas.cogentco.com [154.54.10.90]
10 26 ms 26 ms 26 ms xe-10-2-0.was12.ip4.tinet.net [213.200.81.89]
11 26 ms 26 ms 27 ms peer1-gw.ip4.tinet.net [173.241.128.102]
12 * * * Request timed out.
13 27 ms 26 ms 28 ms badrush.info [64.34.181.15] |
|
| Your not the only one having issues.
I still disconnect about 5 times a day with please connect a valid DSL line.
Um?
Fairpoint told me if I complain to much more I will get disconnected.... |
|
