Same exact issue here with their San Francisco DC and I live less than 50 miles away. I created a new droplet in hopes it would get placed on a different node, and the new droplet was fast at first (like an hour tops) and then it was slow and unresponsive again. I can’t work on my server like this, everything takes too long and it’s beyond frustrating when I can’t even type anything.
Doing a traceroute to the droplet IP showed no hops that were slow or any bottlenecks, so I doubt the issue has anything to do with latency (I get 28ms to the server) or shitty carriers… as mike mentioned above rebooting the droplet does seem to fix the issue temporarily (logging in is fast, typing is fast, everything is fast…)
Not sure why it goes from being fast to terribly slow, especially on fresh droplets that I haven’t even done anything with.
I’m having the same problem. Horrible typing lag over SSH to NY. I just spun up the smallest slice because of the FreeBSD addition. It’s almost unusable; my linodes never have this issue regardless of where the linode is in the USA versus me. I think it lags worse than doing dyndns with my home internet. My pings are in the 50-80ms which should be PLENTY fine for simple SSH command line stuff.
Any ideas why?
Same problem here. Too much lag in SSH. I’ve created the droplet in Singapore and I’m living in India. I also tested AWS instance in Singapore which works awesome without any lag. Please look into this.