For instance, I started from the assumption that the timeout at 4 20 ms * 20 ms 195.66.225.91 << LINX LON1 / Juniper LAN was due to something prior to that, specifically to do with zen. I wouldn't expect that LINX routers are going to timeout on a ping. It's far more likely it was dropped in one direction or the other in the "zen network".
The IP you see isn't a Linx router. It is an IP of a Linx member and will be the Linx member's device. In this case, Fastly, who provide a CDN to BBC.
The Linx member can apply whatever policy they want to their interface, some place very restrictive limits on diagnostic protocols like ICMP so that it can concentrate on the more important job of routing as Ignitionnet as mentioned in a more technical way. Some Linx members don't respond to ICMP at all.
The reverse route may not even be the same from Fastly to the end end user, so the "loss" seen may actually have been caused by a completely different path having an issue outside of the Linx, Zen or Fastly network.
Matt



Pages in this thread:
Print Thread
