Quote:
Originally Posted by chris6273
Awesome cheers! Looks like it's peered at a different node in LINX than the one having issues?
|
To be fair this may be correct but it's not necessarily that simple, often there are many logical links on the same 'node' for private peering vs. public peering, as well as multiple physical links serving each logical link via bonded channels. Last I knew VM used many 10Gbps links into LINX (vs. BT who used fewer ports but running at 100Gbps).
---------- Post added at 19:47 ---------- Previous post was at 19:41 ----------
Quote:
Originally Posted by apcyberax
very possible. Its on a VPS in a IOMark data center. It peers at Linx on 195.66.224.2 If you give me the IP at Linx that is the problem i'll add it to www.ukinternetreport.co.uk so it gets graphed |
It's not actually an IP at LINX that's the problem. The problem appears to lie solely on VM's core network, on some link between their LINX router and Northants. 62.253.174.17 is a good IP to ping if you want to monitor it, although that's only affected when entering via London far as I can tell, traffic from my location on BT to VM bounces via Manchester in one direction and isn't affected (thus, the congestion seems to be unidirectional)