Thread: Anyone else getting really borked speeds this afternoon?
View Single Post
Old 02-01-2012, 16:06   #3
qasdfdsaq
cf.mega poster
 
Join Date: Aug 2004
Posts: 11,207
qasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronze
qasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronze
Re: Anyone else getting really borked speeds this afternoon?
Quote:
Originally Posted by Ignitionnet View Post
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.
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.
qasdfdsaq is offline   Reply With Quote