Hi - I was trying to run some basic performance tests on Spaces recently and after a certain level, the requests were getting rejected with 403s (sample below). Could someone indicate what rate limits are enforced on Spaces (open HTTP connections, max API calls, etc)? Thanks
Upload status 403 Forbidden: resp: &{Status:403 Forbidden StatusCode:403 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[X-Amz-Request-Id:[tx00000000000001037eae3-0059ae1784-8e28-nyc3a] Content-Length:[177] Accept-Ranges:[bytes] Content-Type:[application/xml] Date:[Tue, 05 Sep 2017 03:18:28 GMT] Strict-Transport-Security:[max-age=15552000; includeSubDomains; preload] Access-Control-Allow-Origin:[]] Body:0xc4202849c0 ContentLength:177 TransferEncoding:[] Close:false Uncompressed:false Trailer:map[] Request:0xc4200d22d0 TLS:0xc4200a86e0}
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Shocked I’m seeing this. I’ve been a big DO fan and I’m just coding a simple utility script and it’s saying SlowDown with only TWO files I want to copy within a bucket. So frustrated that something so simple can’t work at the smallest scale. Really reconsidering my commitment with DO and my 4 clients.
Any news? This is still an issue and I’m not reaching the 200 requests per second – or at least provide a detailed log so I have a chance to do a qualified debug.
Digital Ocean. I absolutely love you. BUT, this problem is now unacceptable and inexcusable. We will be moving five separate Spaces servers with over 50 spaces to another provider. We will also be advising 20+ of our clients to make the same move.
You have completely fallen down on the job here, and I can no longer afford to waste hundreds of $$$ of my valuable time dealing with this stupidity. It may be time to start blogging to spread the word on what a failure this is.
Digital Ocean. I absolutely love you. BUT, this problem is now unacceptable and inexcusable. We will be moving five separate Spaces servers with over 50 spaces to another provider. We will also be advising 20+ of our clients to make the same move.
You have completely fallen down on the job here, and I can no longer afford to waste hundreds of $$$ of my valuable time dealing with this stupidity. It may be time to start blogging to spread the word on what a failure this is.
Digital Ocean. I absolutely love you. BUT, this problem is now unacceptable and inexcusable. We will be moving five separate Spaces servers with over 50 spaces to another provider. We will also be advising 20+ of our clients to make the same move.
You have completely fallen down on the job here, and I can no longer afford to waste hundreds of $$$ of my valuable time dealing with this stupidity. It may be time to start blogging to spread the word on what a failure this is.
Digital Ocean. I absolutely love you. BUT, this problem is now unacceptable and inexcusable. We will be moving five separate Spaces servers with over 50 spaces to another provider. We will also be advising 20+ of our clients to make the same move.
You have completely fallen down on the job here, and I can no longer afford to waste hundreds of $$$ of my valuable time dealing with this stupidity. It may be time to start blogging to spread the word on what a failure this is.
Just started using Space and get this error message even with about 1-2 request per seconds or sometimes less: “Please reduce your request rate.”
Even when slowing down to 1 request per 5 seconds I get this error.
Something has to be fixed, in the meanwhile, switching back to AWS S3.
Just started using Space and get this error message even with about 1-2 request per seconds or sometimes less: “Please reduce your request rate.”
Even when slowing down to 1 request per 5 seconds I get this error.
Something has to be fixed, in the meanwhile, switching back to AWS S3.
We are getting rate limited as well. We use spaces to store static assets, and we also put a cdn in front of it, but we are getting repeated reports from our customers of their inability to load the images properly in our e-commerce website. This issue has been going on for quite some time now, and the CDN doesn’t fix it. It’s disappointing because we would like to stay in the DO ecosystem for all the IAS services we need to run our business, but this problem is forcing us out.
Same here… Annoying problem
https://www.digitalocean.com/docs/spaces/ read the limits!
Some how im getting rate limited only for big files.
I just came across this today, trying to upload 1 file. Good thing I caught it in development, Spaces not ready yet.
Error: Maximum response size reached,
i am getting this error, using .net core and using apache as server. any suggestions
Also getting a 503. I set up the space last night and since then have uploaded a total of 5 images. Why is this happening when I am no where near the limiting rate?