High ping to nfoservers !!

[testooo]

Hello,

I am sorry I couldn't find the right forum to post.

I've been playing BF4 for over 2 years and I play on few servers hosted by nfoservers, but I noticed in the last 2 months higher ping (was avg.150ms now avg.175ms) on those servers comparing to last year.


1 <1 ms <1 ms <1 ms GamingRouter [x.x.x.x.x.]
2 9 ms 8 ms 8 ms 10.44.128.1
3 33 ms 88 ms 10 ms soohedrtd01.fln.virtua.com.br [189.4.64.13]
4 9 ms 9 ms 8 ms flndtcrtd01.fln.virtua.com.br [189.4.64.1]
5 13 ms 13 ms 12 ms embratel-T0-0-0-3-uacc02.ctamc.embratel.net.br [201.64.169.45]
6 14 ms 13 ms 19 ms ebt-H0-6-0-3-tcore01.ctamr.embratel.net.br [200.244.211.115]
7 134 ms 136 ms 132 ms ebt-B14551-intl01.atl.embratel.net.br [200.230.230.24]
8 138 ms 138 ms 137 ms ix-et-10-0-2-0.tcore2.a56-atlanta.as6453.net [64.86.9.93]
9 146 ms 143 ms 143 ms 64.86.8.21
10 148 ms 142 ms 158 ms ae-3.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.211]
11 161 ms 162 ms 164 ms ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
12 161 ms 160 ms 160 ms ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.4.153]
13 167 ms 167 ms 168 ms ae-12.r08.chcgil09.us.bb.gin.ntt.net [129.250.2.190]
14 168 ms 166 ms 166 ms ae-31.a00.chcgil09.us.bb.gin.ntt.net [129.250.3.159]
15 173 ms 172 ms 172 ms ntt-1.e7.router1.chicago.nfoservers.com [74.91.119.254]
16 168 ms 166 ms 167 ms c-72-5-195-170.managed-ded.premium-chicago.nfoservers.com [72.5.195.170]

I can see there is a problem on hops 11 - 15, I know ntt is responsible for this routing, I was wondering if nfoservers has any power to get any influence on ntt to fix this problem!

Thank you in advance

[Edge100x]

We have asked NTT about the latency between Atlanta and Chicago previously, as the ~40ms RTT that it takes NTT to go between Chicago and Atlanta is an anomaly compared to some other NSPs (Cogent and Telia, for instance, which take ~15ms between the two cities). They have said that this is normal behavior for their network, but we hope that they improve it in the future. In the meantime, if you email us directly, we can check your outbound path from us to your client to see if it can be improved. You might also consider talking to your ISP and asking them to take a different NSP to reach our prefixes in Chicago.

[testooo]

Thank you so much for the quick reply,

we spoke to the ISP and they can confirm there are no changes in routing on their side, however they said it's outside their control, advising us to contact NTT for this issue as it's an internal routing, also you mentioned that you had contacted NTT so they are aware of it, so I have to wait until they fix it !!!

I really appropriate your help

John

[Edge100x]

This one shouldn't actually be outside your ISP's control, as they can take a different outbound path to reach us. It's us that can't control it from our end, since it is on the inbound =\.

NTT is unlikely to change in the short to medium term, as they do not see this as a problem, and it would require architectural changes in the form of a new physical link between Atlanta and Chicago to reduce latencies between the two cities.

You might also consider moving your service with us to Atlanta, as that should offer a better latency all around for clients near to your own physical location.