Resolved -
We've confirmed that our fix has addressed the issue and workloads are now scheduling normally in all regions.
Apr 8, 22:11 UTC
Update -
Provisioning is recovering for free and paid services across all regions. Free services have resumed serving traffic. We are continuing to monitor for further issues.
Apr 8, 19:44 UTC
Update -
Paid services are continuing to see recovery across builds and deploys. Free services remain disabled and will return errors if loaded in a browser.
Singapore and part of Oregon remain impacted.
Apr 8, 18:48 UTC
Update -
We are continuing to monitor for any further issues.
Apr 8, 18:08 UTC
Update -
We are disabling new free services in Singapore and partially in Oregon.
Apr 8, 16:05 UTC
Monitoring -
We're seeing recovery across all regions.
Apr 8, 15:02 UTC
Update -
We are continuing to work on a fix for this issue.
Apr 8, 15:02 UTC
Update -
We are now seeing the same issue affecting services in Oregon partially. We are investigating to remediate this as quickly as possible.
Apr 8, 14:42 UTC
Identified -
Services with paid compute should now be operating normally. Please note that free services in this region are still intermittently disabled.
Apr 8, 11:23 UTC
Update -
We are continuing to investigate this issue.
Apr 8, 11:22 UTC
Update -
We are seeing some recovery following our mitigation efforts, but we are still working to identify the root cause for a long-term resolution.
Apr 8, 10:54 UTC
Update -
We have temporarily disabled free services in Singapore. We are continuing to investigate and work to mitigate the issue.
Apr 8, 10:31 UTC
Investigating -
This issue may affect new instances during builds, scaling, and similar operations. You may experience build/deploy failures. We are still investigating.
Apr 8, 09:57 UTC