Are new spaces for NYC3 still disabled from 12/10/2018?

Posted January 25, 2019 1.4k views
Object Storage

On 12/4 I received an Email that new space creation on NYC3 would be disabled for several weeks, I have not found an update that normal functionality has returned. I attempted to create a new space today, but it is showing NYC3 as disabled. I was wondering if this is just a temporary disabling, or if this is still a hold over. I have several new projects that I am spinning up and would like to keep everything supported by the same location. If this is still from the previous issue, do you have an updated time for return to normal operation?
Thank you,
Rick (I am a very satisfied customer, just looking for an update)

1 comment

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.

Submit an Answer
3 answers

I imagine this New Incident Report is in reference to my questions and the followup question by @jnmandalakas

  • Its funny because the incident report says its resolved, but I’m still getting the error “Bucket creation temporarily disabled in NYC3; please create your bucket in another region” from the API

    • Will probably have to wait till @jarland is able to advise of what is going on internally. The email I reference said a couple weeks turn around, and while we are past that point, I would hope that a solution is coming soon. I just did not want to go through the hassle of setting up a endpoint outside of NYC3, and then having to migrate back afterwards, or having one droplet with a seperate bucket out from NYC3 then all the other droplets.


They are still disabled for now. I’m afraid I don’t quite have an update on that, but will poke around internally on this.


It would be good to get a timeframe for the restoration of this capability as its blocking deployment of new apps and backups and well need to adjust our infrastructure. Depending on the duration of this, we might need to either use a different region going forward, migrate all of our spaces to a different region or just use AWS S3 as a replacement.