Our GPU utilization is back to normal, and most clients’ serverless queue items have been processed. AWS still hasn’t updated their status page, but we’ll continue monitoring the situation.

We’re beginning to see early signs of recovery in the affected AWS region, and parts of our system are returning to normal operating thresholds. The team is closely monitoring the situation and will continue working on the migration as a precaution.

We're currently working on migrating our services away from the affected AWS region. This may take a few hours. In the meantime, if the AWS region recovers sooner, our services should come back online as well, whichever happens first. Thank you for your patience.

AWS health Status: https://health.aws.amazon.com/health/status

AWS has redeclared the same incident, affecting our API service. We expect this will also impact the console, but nothing yet.

AWS is having a large scale outage that is causing downstream issues on our hosting provider and causing partial or full downtime on console.runpod.io

https://www.vercel-status.com/

Serverless and API calls are also seeing high levels of errors due to AWS outage https://health.aws.amazon.com/health/status

https://downdetector.com/status/aws-amazon-web-services/