Dear Odido,
I hope someone can have a look at this, as this is something within the Odido network and it’s peering agreements. I have asked another Odido member to do a test as well, and they see the same issue. Within 300-450 packets (not ms) we see on the same hop, 2 different internal IP’s show up. In certain cases, hop 5 and 7 for instance will have the exact same IP address (there are often public ones). Now the latter case should not be happening and that points to an unhealthy routing table, or some same weight routing algorithm being applied. The former case can cause out of order packets, which aren’t fun if you are playing an FPS.
The fact that it’s happening so frequently also points to something being a bit odd.
Here is an example taken from another user: hop 3 and 4 being odd
143.177.x.x 7.371 ms 7.297 ms 7.332 ms
2 10.10.12.5 8.170 ms 8.050 ms 7.984 ms
3 80.249.208.1 8.162 ms 7.981 ms
80.249.209.1 8.623 ms
4 80.249.208.1 7.721 ms 7.739 ms 7.858 ms
5 91.200.16.11 8.097 ms 8.114 ms 8.042 ms
6 185.55.136.60 8.661 ms 8.576 ms 8.558 ms
![](https://uploads-eu-west-1.insided.com/tmobile-nl/attachment/6803e1b0-fde6-4753-9f80-980997084022.png)
![](https://uploads-eu-west-1.insided.com/tmobile-nl/attachment/606c1ea1-3c0c-46e5-b9e2-e4940621a6a8.png)