I'll start this by saying I'm on the business service and also a static IP, but I'm curious whether the issue I am seeing is also happening on the residential service.
Earlier this week I suffered a load of drop outs, for the last couple of days it's been back to normal, but, when I do a traceroute I get no TTL expired results (Packet type 11) returned, this means that the responses from the hops are going missing.
Initially I thought it was something on my network, but running a reaceroute directly on the virgin modem diagnostics page shows the same issue, hops are not responding.
While it's normal for some hops not to respond, I'm now seeing no ttl expired messages at all, no matter when I traceroute to.
I'm actually writing a piece of software (https://github.com/fizzyade/pingnoo) which analyses the route and produces realtime graphs of the latency, since the hops all stopped responding obviously this is a bit of an issue when you're developing a piece of software to specifically analyse them!
My normal target is 184.108.40.206, can some people please try running trace routes to this and see what output they get?
As a business customer you need to contact the Business Team.
Pinging 220.127.116.11 with 32 bytes of data: Reply from 18.104.22.168: bytes=32 time=12ms TTL=58 Reply from 22.214.171.124: bytes=32 time=21ms TTL=58 Reply from 126.96.36.199: bytes=32 time=12ms TTL=58 Reply from 188.8.131.52: bytes=32 time=11ms TTL=58
Ping statistics for 184.108.40.206: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 21ms, Average = 14ms
Tracing route to one.one.one.one [220.127.116.11] over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1 2 12 ms 11 ms 9 ms 10.187.16.1 3 10 ms 11 ms 10 ms brad-core-2b-xe-030-0.network.virginmedia.net [18.104.22.168] 4 * * * Request timed out. 5 * * * Request timed out. 6 13 ms 13 ms 11 ms tcma-ic-2-ae9-0.network.virginmedia.net [22.214.171.124] 7 12 ms 11 ms 13 ms 126.96.36.199 8 12 ms 13 ms 9 ms one.one.one.one [188.8.131.52]
Its possible VM are blocking them as you can do that with a cisco switch but as to why? Is odd maybe a DoS attack happened? I used to be able to do ICMP timestamps to 184.108.40.206 till VM stop that so how knows what VM are up to.
@legacy1 wrote: Its possible VM are blocking them as you can do that with a cisco switch but as to why? Is odd maybe a DoS attack happened? I used to be able to do ICMP timestamps to 220.127.116.11 till VM stop that so how knows what VM are up to.
Yep, it seems like a very odd thing to drop from the network. Initially I thought I'd broken my software, but as I delved deeper it became obvious that it was something inside the VM network blocking this specific packets.
Unfortunately, business support is awful, much worse than the residential service where there is at least a community of users.
It doesn't help that this in itself is a bit of a weird issue, in that it's not really an issue for most folks....I just happen to be writing software that it is an issue for!