Depot - Notice history

The system continues to behave as expected and the incident is now resolved.

As of 21:47 UTC we disabled a feature flag that controlled the faulty provisioning system functionality. The system has now stabilized and jobs are processing normally.

We will continue to monitor for any further issues.

This incident has been resolved, all jobs are processing normally.

Container builds in us-east-1 are also processing again, we are monitoring for a full recovery.

We are seeing some recovery for GitHub jobs, but separately are seeing increased start times for container builds in us-east-1.

We have implemented a performance fix and monitoring recovery.

We have deployed a fix for container image builds in us-east-1 and are monitoring recovery. You can now switch back your projects to us-east in your project settings.

We are deploying a mitigation for AWS issues in us-east-1. GitHub Actions jobs continue to be able to process normally, as do container builds in the EU Central region.

We have isolated the outage to only impacting Docker image builders in us-east-1. As a workaround, you can change your project region in Depot to eu-central to bring builds back online.

We have identified an upstream API limit within AWS that has taken down the container image builders. We are seeing some builds that are able to connect and process but are still working on bringing full capacity back online.

This delays appear to be caused by an AWS EC2 API issue, we have raised a support case with AWS

We have deployed a fix and the job queue is processing again.

We now have a workaround in place to force GitHub webhooks to send to Depot.

We are seeing recovery and are going to continue to watch the webhook delivery times.

We are seeing very slow delivery of GitHub Action webhooks but are beginning to see GitHub recover.

We are no longer seeing GitHub networking issues.

We are seeing normal queue times now. We'll continue to monitor.

We have identified that this appears to be issues with GitHub's network ingress returning "HTTP Status: BadGateway."

We'll continue to investigate.

The deploy has completed, build service is restored.

This appears to have been a brief network disruption for our database provider that has since recovered, all jobs and builds are processing normally again.

We are starting to see some recovery, still monitoring