Hi,
I created my first droplet couple of days back on Banglore DC. I am trying to access same from USA and it looks like it shows very high lag.
Also using it via ssh with lags make it difficult to use. Following are snippet of ping command.
Just to know if changing my DC to Asia or Europe would solve this problem?
PING XXX.XX.XX.XX (XXX.XX.XX.XX): 56 data bytes Request timeout for icmp_seq 0 64 bytes from XXX.XX.XX.XX: icmp_seq=0 ttl=46 time=1009.562 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=1 ttl=46 time=1007.247 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=2 ttl=46 time=1006.057 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=3 ttl=46 time=1004.836 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=4 ttl=46 time=1004.675 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=5 ttl=46 time=1008.498 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=6 ttl=46 time=1009.231 ms Request timeout for icmp_seq 8 64 bytes from XXX.XX.XX.XX: icmp_seq=8 ttl=46 time=1009.095 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=9 ttl=46 time=1008.378 ms Request timeout for icmp_seq 11 64 bytes from XXX.XX.XX.XX: icmp_seq=11 ttl=46 time=1008.870 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=12 ttl=46 time=1006.362 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=13 ttl=46 time=1006.554 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=14 ttl=46 time=1007.753 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=15 ttl=46 time=1005.372 ms Request timeout for icmp_seq 17 64 bytes from XXX.XX.XX.XX: icmp_seq=17 ttl=46 time=1006.765 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=18 ttl=46 time=1006.453 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=19 ttl=46 time=1007.759 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=20 ttl=46 time=1005.189 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=21 ttl=46 time=1004.227 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=22 ttl=46 time=1006.418 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=23 ttl=46 time=278.888 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=24 ttl=46 time=1008.178 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=25 ttl=46 time=1004.993 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=26 ttl=46 time=281.633 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=27 ttl=46 time=1007.910 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=28 ttl=46 time=289.008 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=29 ttl=46 time=1006.386 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=30 ttl=46 time=1004.721 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=31 ttl=46 time=771.703 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=32 ttl=46 time=1006.595 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=33 ttl=46 time=1006.524 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=34 ttl=46 time=1008.401 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=35 ttl=46 time=1004.929 ms ^C — XXX.XX.XX.XX ping statistics — 37 packets transmitted, 33 packets received, 10.8% packet loss round-trip min/avg/max/stddev = 278.888/933.914/1009.562/209.688 ms
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi!
I’m sorry to hear that you’re experiencing bad network performance—that is certainly not supposed to be the case, even when you’re accessing a BLR Droplet from the USA! Please open a support ticket so that the team can investigate and see what’s causing the high latency.
Though, in general, moving your Droplet to a region that is geographically closer to you will greatly improve latency.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.