arrow_back Ping to AWS servers, network routing priority?

1 vote
I'll try to be brief, but I'll also try to be detailed:

I live in the suburbs of Lviv (Ukraine, near Poland). I play the game professionally, I connect to Frankfurt AWS servers (Europe (EU Central 1) (Frankfurt)

I don't use router, 5 months there were problems with packetloose, when ping became 27 ms. A million times wrote an appeal to the administrators of the provider, finally after months they said that "reconnect us to other servers". Packetloose almost disappeared, but the ping went up to 40 (The game is very ping-dependent, so it was a punch below the belt).

Another month of appeals to the provider and I was brought Microtic, I was told to connect. Once I connected as the ping was 28 ms, at the same moment, disconnected and reconnected directly -- 27 ms. (It would seem that the response is back to normal, and also without packetloose). The interesting thing is that I live in a city of 10 000 inhabitants, and all these changes affected also my friends from that city (judging by the common sense logic it is unlikely that Microtic could affect the entire network in our city, probably a coincidence). The provider said that he would not change anything else.

But it didn't last long - 2 weeks later packets started to be routed through Kyiv server again, not directly to Frankfurt and the ping, as it was then, went up to 40 ms. The question is - why is it so and how can I fix it? The connection is not going directly to Europe, but first it is going to the East to Kiev and then back. I just can't find out what is the problem from my ISP, because even the tiniest problem solving is an incredibly drawn-out process of unanswered questions and inarticulate and indecisive answers from their support. I suspect that they have "reconnected us to other servers" again, although I don't even know what that means.

If possible, point me to the reason for this routing and ping increase, so that at the very least it would be easier for me to talk to ISP support about the problem, I would really appreciate it.


2 Answers

Best answer
0 votes
It is unlikely that anything can be done, because the provider leases transmission channels and nodes from backbone providers, and switching some segment to another branch may be impossible or economically unprofitable.
It's hard to say in your case. Maybe the ISP, in order to get away with it, switched the vag to another branch, offered a router to increase the ping, and then brought it back. That's business.
If there are other providers in your city, maybe they have different routing, but very big doubt about it.
If all the Internet goes on this route, it is hardly possible to do anything at all, if not, then the inclusion of some access node (VPN) to bypass this route can improve the situation. It is necessary to carefully analyze the network and routing
0 votes
The difference between a ping of 27 and 40 an ordinary person is difficult to discern. And if it is distinguishable - the body's response time is so much longer that the ping on its background does not matter (spoiler - the reaction time to the expected visual signal is on average 160 ms, on the first link you can check yourself).

1 comment

That wasn't the question...