Consolidated Communications → Re: Constant bad latency/pings to game server

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.

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.

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:

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.

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.

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....