I have a server in NYC2. I regularly back up 150 MB of data from NYC2, to Amazon S3, in their Oregon region. It’s very slow.
I ran these tests AFTER this morning’s NTT network changes. There was no improvement.
150 MB upload from VPS to an Amazon S3 bucket in the us-west-2 (Oregon) region
- Digital Ocean, from NYC2 (2 GB instance): 11:50
- Digital Ocean, from SFO1 (2 GB instance): 3:35
- Linode, from New Jersey (1 GB instance): 0:25
For this upload, DO/NYC2 is 25-30 times slower than Linode/NJ. What’s going on?
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!
Note: Although all three traceroutes show a different IP address, the hostname was the same in all cases. Unfortunately, the full hostname had to be redacted, but it was just a CNAME for s3-us-west-2-w.amazonaws.com.
Hi, <br> <br>Please provide the traceroutes from each location so we can review, without that information there isn’t much info that we can troubleshoot against. <br> <br>Thanks
Google “bandwidth delay product” and tune your tcp/ip stacks for the desired performance that you want. DigitalOcean uses default settings. You can get any host to go faster or slower on transfers to anywhere with a little tuning.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.