No. I have 180ms stable ping to news.YC, stable 40ms ping to Google. It's not a line problem.
Chrome Dev Tools show me that I receive content within 300-400ms of hitting the page with all the images loading in about 2-3 seconds... and then there's one huge 1 minute line associated with "platform.twitter.com", "static.ak.fbcdn.net", "www.stumbleupon.com" (everything else being a short ticks with 50-100ms receive time - it's a real 35Mbps line)
Any site that I measure with Chrome Dev Tools in any part of the world is fast (seconds, milliseconds), the only parts that are slow quite sometimes are those guys - T, FB, SU.
And yes - those are very long delay. Maybe Twitter and FB have some peering problems - I don't know. I don't need to know. It's just that those can be fixed easily so that we don't have to find out why T/FB have peering problems.
For what it's worth, I often see this problem in Canada - it's not always the offenders you list, but third-party widgets do significantly slow down page loads relatively often.
platform.twitter.com runs on akamai. Maybe there is a problem with the russian akamai mirror(s)? I don't know if facebook and stumbleupon use akamai, too.
Chrome Dev Tools show me that I receive content within 300-400ms of hitting the page with all the images loading in about 2-3 seconds... and then there's one huge 1 minute line associated with "platform.twitter.com", "static.ak.fbcdn.net", "www.stumbleupon.com" (everything else being a short ticks with 50-100ms receive time - it's a real 35Mbps line)
Any site that I measure with Chrome Dev Tools in any part of the world is fast (seconds, milliseconds), the only parts that are slow quite sometimes are those guys - T, FB, SU.
And yes - those are very long delay. Maybe Twitter and FB have some peering problems - I don't know. I don't need to know. It's just that those can be fixed easily so that we don't have to find out why T/FB have peering problems.