Lack of SE Response to Lag

[Rivienne]

Rubberbanding, i would say 60+% of the time, is a local issue. As in your city, your street, your house, your router, your nic.

Want to test it? bring your computer to a friend's house and hook into their router, and see if the same issues occur.

Don't half-ass it by tapping into a shared wireless network at apartments or something.

If no troubles, the issue is confirmed local. If yes, then we can talk.

Don't want to test it? Then don't expect us to consider your concerns as valid.

Just want to point out, if you want to help people troubleshoot, you might want to actually read more of the posts. If you had done much reading up on these forums posts (including over in tech support) you would see it isn't local, it is very specifically in level3 for a larger percentage of people complaining. Specifically the same addresses set in level3.

The majority of people are complaining about a new issue, that affects entire ISP's that are routing through that level3 address. I can personally verify this problems occurs in 5 locations across 2 states now. The one thing they all have in common is that they are routed through the same node in montreal. If you can get a VPN address that routes around that node.. Problem goes away.

The problem could be in isp, or it could be in level3, but is isn't remotely local. I am sure some people complaining have a different issue entirely, but the majority of these new posts/threads are about the new rubberbanding that is caused by specific hops. The traceroutes should be enough for you recognize this. When traceroutes from the UK, Canada, US in both eastern and western, all show packet loss, at the same address at Level3, there is clearly more going on.