Quote:
Originally Posted by qasdfdsaq
Interesting, return path only congestion. I hadn't thought of that. I forget these things are bidirectional sometimes. Was curious why the JANET trace only spiked on the second hop outside VM.
I wonder why today though... Locally my TB graph looks fairly tame overall.
Also I'd assumed OVH's sw1.tc.lon.ovh.net meant telecity but the IP is a LINX peer too, so yes it looks like a VM <=> LINX problem.
|
There's a LINX PoP in several Telecity facilities.
https://www.linx.net/about/partnerpages/telecity.html