Ping to AWS servers, network routing priority?

Question

Computer networks

I will try to be brief, but also in detail:

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

I don't use a router, for 5 months there were problems with packetlus, when the ping became 27 ms. A million times I wrote an appeal to the administrators of the provider, in the end, months later, they said that they would "reconnect us to other servers." Packets are almost gone, but the ping went up to 40 (The game is very ping dependent, so it was a blow below the belt).

Another month of calls to the provider and they brought me Mikrotik, they said to connect it. As soon as I connected, the ping became 28 ms, at the same moment, disconnected and reconnected directly - 27 ms. (It would seem that the response returned to normal, and even without packet loops). It is interesting that I live in a city with 10,000 inhabitants and all these changes also affected my friends from this city (judging by sound logic, it is unlikely that Mikrotik could affect the entire network in our city, probably a coincidence). The provider said that he would not change anything else.

But the song did not play for long - 2 weeks later the packets again started to be routed through the fiord.net Kyiv server, and not directly to Frankfurt, and the ping, as then, rose to 40 ms. The essence of the question is the following - why is this happening and can I somehow fix it on my part? The connection does not go directly to Europe, but first goes east to Kyiv, and then back. I can’t find out what’s wrong with the provider, since solving even the smallest tasks is an incredibly protracted process of unanswered calls and slurred and indecisive support answers. I suspect that they "reconnected" us to other servers again, although I don't even understand what that means.

If possible, point me to the reason for such routing and ping increase, so that at least it would be easier for me to talk to the provider's support about the problem, I would be very grateful.

Answer 1

It is unlikely that anything can be done, because the provider leases transmission channels and nodes from backbone providers, and it may be impossible or economically unprofitable to switch some segment to another branch.
It's hard to say which is your case. Perhaps the provider, in order to get rid of it, switched the locality to another branch, offered a router to increase the ping, and then returned it back. This is business.
If there are other providers in your city, then they may have a different routing, but there are very big doubts about this.
If the entire Internet goes along this route, then it is hardly possible to do anything at all, if not, then turning on some kind of access node (vpn) to bypass this route can improve the situation. It is necessary to carefully analyze the network and routing

Answer 2

The difference between a ping of 27 and 40 by an ordinary person is difficult to discern. And if it is distinguishable - the response time of the body is so much longer that ping is not important against its background (spoiler - the reaction time to the expected visual signal is on average 160 ms, you can check yourself at the first link).
Relevant links:
https://humanbenchmark.com/tests/reactiontime
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4456887/