Hi , can you please help me to understand why i get many request timeout on this IP adress 188.8.131.52 ??
The ip 184.108.40.206 appears to be located in Paris, France and allocated to RIOT-NA1. Autonomous System Number (ASN) code for 220.127.116.11 is AS6507. IP Address local time zone is Europe/Paris (+0200). PTR record is set to 18.104.22.168.
I can't fiind where is the problem ... Im changing ISP .. from TT to VM .. What can i do ?
Can't explain why it's an issue, but it's an issue for me too - i can't reach the IP address via a traceroute either - it stops at the same place as yours, which is a liberty global address belonging to their ISP in the Netherlands, Cello.
I can reach it via my other ISP though, and it's a pretty direct path via the London Internet Exchange (LINX).
For occasional use then (for example) the free VPN built into the Opera browser might overcome that? A paid VPN would perform more robustly if your access needs required something speedy and reliable.
Obviously it would be better if VM fixed their routing, but getting that sort of thing looked at is difficult because VM's organisational design prevents customers speaking to those staff who'd understand the issue, take ownership, investigate and get it resolved. You might get lucky if the forum staff pick this up and decide to pass it to the right people, but given the international dimension you're hoping for quite a lot of stars to align.
If it's a deal breaker and you're still in your cooling off period, you might want to decide whether VM is the way forward for you.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
I'm no longer on a VM connection due to personal circumstances, so my tracert is done over BT
Tracing route to 22.214.171.124 over a maximum of 30 hops
1 1 ms <1 ms <1 ms bthub [192.168.1.254]
2 4 ms 4 ms 5 ms 172.16.19.151
3 * * 17 ms 126.96.36.199
4 17 ms 17 ms 17 ms 188.8.131.52
5 17 ms 17 ms 17 ms 184.108.40.206
6 26 ms 19 ms 17 ms peer1-et7-0-2.interxion.ukcore.bt.net [220.127.116.11]
7 17 ms 17 ms 19 ms linx-j.riotdirect.net [18.104.22.168]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
First off - just because a tracert doesn't appear to reach it's target doesn't mean that target is unreachable.
When a normal packet is sent across the internet it's given a TTL value (In Windows this defaults to 64), every time the packet passes through a node the TTL value is reduced. If the TTL gets to 0 BEFORE the packet reaches it's destination then we get a ICMP Destination Unreachable error returned.
Normally most packets will actually get to their destination before the TTL reaches 0.
Tracert makes use of this by sending out packets with TTL starting at 1 and then increasing until either:
The response shows a source = target IP
The hop limit for the tracert is reached (defaults to 30 but can be amended with the -h parameter)
However a target can be set not to respond to ICMP echo packets. In which case the first condition is never reached - even on a good connection. It's worth knowing this as it can save a lot of head scratching.
However my last recorded packet does show successful peering between BT and Riot Games network:
6 26 ms 19 ms 17 ms peer1-et7-0-2.interxion.ukcore.bt.net [22.214.171.124] 7 17 ms 17 ms 19 ms linx-j.riotdirect.net [126.96.36.199] 8 * * * Request timed out.
P.S. I've got my pedantic head on so I just wanted to point out this:
PTR record is set to 188.8.131.52.
is not correct.
A PTR record is used when doing a reverse DNS search, If you do nslookup with an IP address then you get the result of a DNS query where the octets are reversed and the parent domain in-addr.arpa is added. If you have access to dig you can do this: