Monitoring - all services are returning to normal operating baselines, however we are continuing to monitor overall service recovery.

On April 10, 2025, between 18:26:30 UTC and 18:53:00 UTC, a service disruption occurred due to a software release that was dependent on a database change which had not yet been applied. This caused our primary API to become temporarily non-functional. As a result, customers experienced issues including missing pods and serverless endpoints in the dashboard, and delayed request processing due to serverless endpoints being unable to scale.

Identified - This issue is caused by a database problem. We've applied the fix and are continuing to monitor recovery.

Investigating - We are currently experiencing an issue with RunPod console and API where users are not able to access or deploy new Pods and Serverless endpoints.
We are currently investigating and will post an update as soon as we are able.