S3 access for EU-RO-1 has been down for days but no update from the team?
As you can see from the various posts (including my own) reporting the same problem, S3 access for network volumes on the EU-RO-1 region has been down for the past couple of days.
I can fully understand that things like that can happen from time to time. However, the lack of status update or even acknowledgement of the problem from the company made me concerned.
I recently switched the rendering backend of my service to RunPod and I've been testing it before it goes production. However, the lack of feedback on such a critical issue made me seriously wonder if I made a bad move, and should keep the AWS-based solution that I was using instead.
Increased overhead due to RunPod not having a datacenter in the Asia Pacific region made it difficult to persuade people for migrating to RunPod.
But now, I don't know what should I do if things like that happen on a production service. And I'm not sure if I'll have a good argument if people insist to go back to the AWS backend.
3 Replies
We receive alerts when S3 access is offline. Have you contacted support with this issue so I can check if you were well taken care of?
No. I thought it'd be faster to get a respond here, especially when I saw similar problem was already reported by others.
I'll open a support ticket as suggested. Thanks!
Support can help follow through, I just want to make sure you were treated well if you had already reached out. I'm happy to do/be support, I just have a little more flexibility than they do in some regards.