![]() |
Anyone else getting really borked speeds this afternoon?
Certain destinations seem to have a lag spike of ~100ms and pretty bad speeds as a result:
BBC - Fine: Code:
C:\Users\Administrator>tracert www.bbc.co.ukCode:
C:\Users\Administrator>tracert s2.qasdfdsaq.comCode:
C:\Users\Administrator>tracert www.ja.netCode:
traceroute to d.qasdfdsaq.com (92.235.190.31), 30 hops max, 60 byte packets |
Re: Anyone else getting really borked speeds this afternoon?
Seeing it, yes, any idea, I blame the return path as the forward looks fine. I reckon 195.66.224.23 is maxed out inbound or is in strife. Wouldn't be the first time VM have allowed a LINX port to saturate and won't be the last so that's why the first thought is overloaded peering.
Code:
traceroute to www.ja.net (212.219.98.101), 30 hops max, 40 byte packetsCode:
traceroute to s2.qasdfdsaq.com (178.32.52.252), 30 hops max, 40 byte packetsCode:
traceroute to 195.66.224.23 (195.66.224.23), 30 hops max, 40 byte packetsCode:
# Host Sent Recvd Best Avg Worst |
Re: Anyone else getting really borked speeds this afternoon?
Quote:
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. |
Re: Anyone else getting really borked speeds this afternoon?
a few heads eating away a bit of paid bandwidth! pings are shot as a result too.. aahh the joys of paying for services!
|
Re: Anyone else getting really borked speeds this afternoon?
Quote:
https://www.linx.net/about/partnerpages/telecity.html |
| All times are GMT. The time now is 13:22. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum