latency variation on CS:GO LA and CHI servers

[furial]

Hello

I been playing on some csgo servers LA with 6-12 ping and CHI 58-60 ping but lately its been increasing during the day to 45-55 ping on LA and 80-88 ping on CHI servers.

Any idea on what is causing this latency variations?

2 ms 1 ms 1 ms 201.143.182.185.ded.telnor.net [201.143.182.185]
7 ms 6 ms 6 ms bb-la-grand-10-ae11_0.uninet.net.mx [189.246.220.86]
* * 45 ms las-b23-link.ip.twelve99.net [213.248.84.173]
45 ms 45 ms 45 ms las-b22-link.ip.twelve99.net [62.115.143.39]
45 ms 44 ms 45 ms telia.e9.router.la.nfoservers.com [162.248.93.254]
45 ms 45 ms 45 ms c-104-153-109-203.premium-la.nfoservers.com [104.153.109.203]

2 ms 1 ms 1 ms 201.143.182.185.ded.telnor.net [201.143.182.185]
6 ms 6 ms 5 ms bb-la-grand-10-ae11_0.uninet.net.mx [189.246.220.86]
45 ms 45 ms 45 ms las-b21-link.ip.twelve99.net [62.115.32.37]
* * * Request timed out.
45 ms 45 ms 45 ms las-b22-link.ip.twelve99.net [62.115.143.39]
45 ms 45 ms 45 ms telia.e9.router.la.nfoservers.com [162.248.93.254]
46 ms 45 ms 45 ms v-104-153-109-186.unman-vds.premium-la.nfoservers.com [104.153.109.186]

2 ms 4 ms 1 ms 201.143.182.185.ded.telnor.net [201.143.182.185]
6 ms 6 ms 6 ms bb-la-grand-10-ae11_0.uninet.net.mx [189.246.220.86]
45 ms 45 ms 45 ms las-b21-link.ip.twelve99.net [62.115.32.37]
* * * Request timed out.
45 ms 45 ms 45 ms las-b22-link.ip.twelve99.net [62.115.143.39]
45 ms 45 ms 45 ms telia.e9.router.la.nfoservers.com [162.248.93.254]
47 ms 45 ms 45 ms v-162-248-93-5.unman-vds.premium-la.nfoservers.com [162.248.93.5]

2 ms 1 ms 1 ms 201.143.182.185.ded.telnor.net [201.143.182.185]
6 ms 6 ms 6 ms bb-la-grand-10-ae11_0.uninet.net.mx [189.246.220.86]
* 45 ms * las-b23-link.ip.twelve99.net [213.248.84.173]
45 ms 1681 ms 45 ms las-b22-link.ip.twelve99.net [62.115.143.39]
45 ms 44 ms 45 ms telia.e9.router.la.nfoservers.com [162.248.93.254]
45 ms 107 ms 45 ms c-162-248-93-9.premium-la.nfoservers.com [162.248.93.9]

2 ms 1 ms 1 ms 201.143.182.185.ded.telnor.net [201.143.182.185]
6 ms 6 ms 5 ms bb-la-grand-10-ae11_0.uninet.net.mx [189.246.220.86]
* 46 ms 45 ms las-b23-link.ip.twelve99.net [213.248.84.173]
45 ms 45 ms 45 ms dls-b23-link.ip.twelve99.net [62.115.123.136]
63 ms 63 ms 63 ms atl-b24-link.ip.twelve99.net [80.91.246.74]
76 ms 76 ms 76 ms chi-b23-link.ip.twelve99.net [62.115.113.19]
62 ms 61 ms 61 ms telia-2.e5.router2.chicago.nfoservers.com [74.91.119.253]
77 ms 76 ms 76 ms c-74-91-115-50.premium-chicago.nfoservers.com [74.91.115.50]

2 ms 1 ms 1 ms 201.143.182.185.ded.telnor.net [201.143.182.185]
6 ms 5 ms 6 ms bb-la-grand-10-ae11_0.uninet.net.mx [189.246.220.86]
45 ms * * las-b23-link.ip.twelve99.net [213.248.84.173]
45 ms 45 ms 45 ms dls-b23-link.ip.twelve99.net [62.115.123.136]
63 ms 63 ms 63 ms atl-b24-link.ip.twelve99.net [80.91.246.74]
76 ms 76 ms 76 ms chi-b23-link.ip.twelve99.net [62.115.113.19]
62 ms 61 ms 61 ms telia-1.e7.router2.chicago.nfoservers.com [64.74.97.253]
77 ms 76 ms 76 ms d-72-5-195-31.ded-machine.premium-chicago.nfoservers.com [72.5.195.31]

2 ms 1 ms 1 ms 201.143.182.185.ded.telnor.net [201.143.182.185]
6 ms 5 ms 5 ms bb-la-grand-10-ae11_0.uninet.net.mx [189.246.220.86]
46 ms 45 ms * las-b23-link.ip.twelve99.net [213.248.84.173]
45 ms 45 ms 45 ms las-b22-link.ip.twelve99.net [62.115.143.39]
* 46 ms * dls-bb1-link.ip.twelve99.net [62.115.118.246]
71 ms 67 ms 65 ms nash-bb1-link.ip.twelve99.net [62.115.137.44]
* 63 ms * atl-bb1-link.ip.twelve99.net [62.115.137.54]
63 ms 63 ms 63 ms atl-b24-link.ip.twelve99.net [62.115.134.247]
77 ms 77 ms 77 ms chi-b23-link.ip.twelve99.net [62.115.134.11]
62 ms 62 ms 62 ms telia-2.e5.router2.chicago.nfoservers.com [74.91.119.253]
77 ms 77 ms 77 ms c-74-91-119-147.managed-vds.premium-chicago.nfoservers.com [74.91.119.147]

Thank you in advance

[TimeX]

In each of those, there is an increase of about 40ms between uninet.net.mx and twelve99.net, but everything looks normal otherwise. Do you have any results from before problems started, for comparison?

[furial]

I don't but i noticed a small latency decrease on both LA and CHI servers

Tracing route to c-104-153-109-203.premium-la.nfoservers.com [104.153.109.203]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms xxx.xxx.x.x
2 1 ms 1 ms 1 ms 201.143.182.185.ded.telnor.net [201.143.182.185]
3 6 ms 6 ms 6 ms bb-la-grand-10-ae11_0.uninet.net.mx [189.246.220.86]
4 * * * Request timed out.
5 37 ms 36 ms 36 ms las-b22-link.ip.twelve99.net [62.115.143.39]
6 37 ms 36 ms 36 ms telia.e9.router.la.nfoservers.com [162.248.93.254]
7 36 ms 38 ms 36 ms c-104-153-109-203.premium-la.nfoservers.com [104.153.109.203]

Tracing route to v-104-153-109-186.unman-vds.premium-la.nfoservers.com [104.153.109.186]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms xxx.xxx.x.x
2 1 ms 1 ms 957 ms 201.143.182.185.ded.telnor.net [201.143.182.185]
3 6 ms 6 ms 6 ms bb-la-grand-10-ae11_0.uninet.net.mx [189.246.220.86]
4 37 ms 36 ms 36 ms las-b21-link.ip.twelve99.net [62.115.32.37]
5 * * * Request timed out.
6 40 ms 934 ms 37 ms las-b22-link.ip.twelve99.net [62.115.143.39]
7 37 ms 36 ms 36 ms telia.e9.router.la.nfoservers.com [162.248.93.254]
8 37 ms 36 ms 37 ms v-104-153-109-186.unman-vds.premium-la.nfoservers.com [104.153.109.186]


Tracing route to v-162-248-93-5.unman-vds.premium-la.nfoservers.com [162.248.93.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms xxx.xxx.x.x
2 2 ms 1 ms 1 ms 201.143.182.185.ded.telnor.net [201.143.182.185]
3 6 ms 6 ms 6 ms bb-la-grand-10-ae11_0.uninet.net.mx [189.246.220.86]
4 37 ms 37 ms 37 ms las-b21-link.ip.twelve99.net [62.115.32.37]
5 * * * Request timed out.
6 36 ms 36 ms 36 ms las-b22-link.ip.twelve99.net [62.115.143.39]
7 36 ms 36 ms 36 ms telia.e9.router.la.nfoservers.com [162.248.93.254]
8 37 ms 36 ms 37 ms v-162-248-93-5.unman-vds.premium-la.nfoservers.com [162.248.93.5]

Tracing route to c-74-91-115-50.premium-chicago.nfoservers.com [74.91.115.50]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms xxx.xxx.x.x
2 2 ms 1 ms 1 ms 201.143.182.185.ded.telnor.net [201.143.182.185]
3 6 ms 6 ms 6 ms bb-la-grand-10-ae11_0.uninet.net.mx [189.246.220.86]
4 * * * Request timed out.
5 37 ms 36 ms 36 ms dls-b23-link.ip.twelve99.net [62.115.123.136]
6 59 ms 59 ms 59 ms c-74-91-115-50.premium-chicago.nfoservers.com [74.91.115.50]


Tracing route to d-72-5-195-31.ded-machine.premium-chicago.nfoservers.com [72.5.195.31]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms xxx.xxx.x.x
2 1 ms 1 ms 1 ms 201.143.182.185.ded.telnor.net [201.143.182.185]
3 6 ms 5 ms 5 ms bb-la-grand-10-ae11_0.uninet.net.mx [189.246.220.86]
4 * * * Request timed out.
5 36 ms 36 ms 37 ms dls-b23-link.ip.twelve99.net [62.115.123.136]
6 60 ms 59 ms 59 ms d-72-5-195-31.ded-machine.premium-chicago.nfoservers.com [72.5.195.31]

Could it be a routing problem from my ISP?

[TimeX]

That is showing the same problem as before, except the latency increase is only 30ms instead of 40ms. It does seem to be some sort of routing/peering issue with your ISP, but it looks like it is starting to improve at least.

[Edge100x]

It does look like your ISP changed something about its connection to Telia there. They may have been overloading it before, and stopped overloading it (at least temporarily).

Troubleshooting with Telia can be difficult sometimes because Telia's network randomly mangles TTLs, resetting the number to some high value partway through the path. This can cause traces to show only part of the path, followed by the endpoint.

[alexis92]

I had been facing similar issues with CS:GO on the South Asian servers, but it seemed to resolve itself after persisting for about a week,. Might just be ISP-related after all to be honest.