All systems operational

Builds

99.85% uptime
Aug 2023 · 99.72%Sep · 99.89%Oct · 99.96%
Aug 202399.72% uptime
Sep 202399.89% uptime
Oct 202399.96% uptime
API
99.97% uptime
Aug 2023 · 99.92%Sep · 100.0%Oct · 100.0%
Aug 202399.92% uptime
Sep 2023100.0% uptime
Oct 2023100.0% uptime

Depot-managed GitHub Actions Runners

100.0% uptime
Aug 2023 · 100.0%Sep · 100.0%Oct · 100.0%
Aug 2023100.0% uptime
Sep 2023100.0% uptime
Oct 2023100.0% uptime
Website
100.0% uptime
Aug 2023 · 100.0%Sep · 100.0%Oct · 99.99%
Aug 2023100.0% uptime
Sep 2023100.0% uptime
Oct 202399.99% uptime
Github - Actions
Operational

Notice history

Oct 2023

Issue downloading Depot CLI
  • Resolved
    Resolved

    We have deployed a mitigation to work around Cloudflare's KV outage, the download server is returning success responses.

  • Investigating
    Investigating

    A Cloudflare outage is currently affecting downloads of the Depot CLI. We are investigating potential mitigations.

Degraded build performance in eu-central-1 region
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    We've deployed an initial fix, builds in eu-central-1 are running on primary infrastructure again. We're monitoring the fix.

  • Investigating
    Investigating

    We are currently investigating degraded build performance in eu-central-1 - a number of build jobs are automatically re-routing to backup infrastructure and may experience reduced caching performance during this time.

Builds machines failing to launch
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    We have deployed our fix, and we are seeing builds recovering. We will continue to monitor builds coming back online.

  • Identified
    Update

    We are deploying a fix to our control plane to workaround the Quay outage.

  • Identified
    Update

    We have identified the issue as being at the Quay registry and are currently monitoring that outage while working on a fix: https://status.quay.io/.

  • Identified
    Identified

    We have identified the issue as being at the Quay registry and are currently monitoring that outage while working on a fix: https://status.quay.io/.

Sep 2023

failed to read dockerfile: failed to load cache key: no handler for git
  • Resolved
    Resolved

    The queue backlog is clear, build start time has returned to fast.

  • Monitoring
    Monitoring

    We are monitoring the rollout of the fix, we are currently waiting on a queue backlog

  • Resolved
    Resolved

    We have deployed a fix, the error has cleared

  • Investigating
    Investigating

    We are investigating an issue causing some builds to fail with the message "failed to read dockerfile: failed to load cache key: no handler for git".

Builders failing to launch
  • Resolved
    Resolved

    We've deployed a fix and will continue to monitor the results.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result.

  • Investigating
    Investigating

    We are currently investigating this incident.

Issues starting builds
  • Resolved
    Resolved

    We've deployed a fix to address this and are continuing to monitor it.

  • Investigating
    Investigating

    We are currently investigating an issue that is causing some builds to fail to start.

Aug 2023

Issue starting builds
  • Resolved
    Resolved

    We have deployed a fix, build service is restored.

  • Investigating
    Investigating

    We are currently investigating an issue preventing build machines from starting.

API Outage
  • Resolved
    Resolved

    A database fix is deployed, API service is restored

  • Identified
    Identified

    We have identified a database issue as the outage cause and are working to remediate.

  • Investigating
    Investigating

    We are investigating an API outage.

Builders failing to launch in us-east
  • Resolved
    Resolved

    This incident has been resolved, build service is restored

  • Identified
    Update

    This capacity issue only exists in the us-east region, and we have capacity available in the eu-central region. You can change your region via the project settings.

  • Identified
    Identified

    We have identified the issue and are working with our hosting provider to get additional capacity.

  • Investigating
    Investigating

    We are currently investigating an issue that is causing builders to fail to launch.

AWS us-east-1 outage
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    All builds are now using primary infrastructure, we are monitoring to ensure that all service is restored.

  • Identified
    Update

    AWS is reporting that the us-east-1 outage has cleared, we are routing builds back to primary infrastructure.

  • Identified
    Update

    AWS is experiencing an outage in us-east-1 (https://health.aws.amazon.com/health/status). We are attempting a failover to backup infrastructure in another region.

  • Identified
    Update

    AWS is still experiencing issues in us-east-1, we are prepping to fail over to backup infra.

  • Identified
    Identified

    AWS us-east-1 is currently rate-limiting infrastructure updates, we are monitoring.

  • Investigating
    Investigating

    We are investigating lag in acquiring build machines, causing some build requests to time out.

Aug 2023 to Oct 2023