Depot - Notice history

All systems operational

100% - uptime

us-east-1 - Operational

100% - uptime
Jan 2025 · 99.91%Feb · 99.93%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

eu-central-1 - Operational

100% - uptime
Jan 2025 · 99.96%Feb · 99.93%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

us-west-2 - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025
100% - uptime

Depot-managed Actions Runners - Operational

100% - uptime
Jan 2025 · 99.94%Feb · 99.93%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Github.com - Actions - Operational

API - Operational

100% - uptime
Jan 2025 · 99.96%Feb · 99.99%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Website - Operational

100% - uptime
Jan 2025 · 99.96%Feb · 99.99%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Notice history

Mar 2025

Longer GitHub Actions queue times
  • Resolved
    UTC
    Resolved

    Queue times have returned to normal.

  • Investigating
    UTC
    Investigating

    We are currently investigating possible delays in Actions jobs starting.

macOS runners failing to launch
  • Resolved
    UTC
    Resolved

    Build service is restored. The underlying cause was an issue with a certificate / system time in the macOS VM image itself. We have deployed a working image to all macOS hosts.

  • Monitoring
    UTC
    Monitoring

    We are currently deploying a fix to all macOS hosts, build service is beginning to be restored.

  • Identified
    UTC
    Identified

    We have identified the potential root cause and are working on populating a fix out across the fleet of compute for macOS runners.

  • Investigating
    UTC
    Investigating

    We are currently investigating an issue with macOS runners for GitHub Actions not launching.

GitHub outage
  • Resolved
    UTC
    Resolved

    GitHub have marked their incident as resolved.

  • Monitoring
    UTC
    Monitoring

    We are currently monitoring the ongoing GitHub outage that is impacting GitHub Actions and other services: https://www.githubstatus.com/incidents/lb0d8kp99f2v

Feb 2025

Website and API outage
  • Resolved
    UTC
    Resolved

    Build service has fully restored.

  • Update
    UTC
    Update

    Build and Action jobs are starting to process, we are working through the backlog of jobs from the disruption.

  • Identified
    UTC
    Identified

    We have deployed a mitigation and are seeing service begin to be restored.

  • Investigating
    UTC
    Investigating

    We are currently investigating an API and website outage.

Longer queue times for GitHub Actions
  • Resolved
    UTC
    Resolved

    Queue times have returned to normal.

  • Investigating
    UTC
    Investigating

    We are investigating alerts about longer queue times for Actions jobs.

GitHub Incident
  • Resolved
    UTC
    Resolved

    GitHub have resolved their incident.

  • Investigating
    UTC
    Investigating

    GitHub are currently experiencing an incident - affected GitHub jobs have increased queue time while GitHub works through the backlog of job notifications and should eventually be processed.

Longer queue times for some GitHub Actions jobs
  • Resolved
    UTC
    Resolved

    GitHub have resolved their incident.

  • Monitoring
    UTC
    Monitoring

    We are currently observing some increase in queue times for GitHub Actions jobs - GitHub are currently experiencing an incident that may be related. We are monitoring.

Application database outage
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring

    We implemented a fix and are currently monitoring the result. Job are slowly being picked up.

  • Investigating
    UTC
    Investigating

    We are currently investigating an incident affecting our primary application database.

Jan 2025

Application database outage
  • Resolved
    UTC
    Resolved

    We are seeing full connectivity restored, builds are processing normally.

  • Monitoring
    UTC
    Monitoring

    We are seeing database connectivity restore, builds are able to process now with degraded performance.

  • Investigating
    UTC
    Investigating

    We are currently investigating an incident affecting our primary application database.

Some GitHub jobs waiting to start
  • Resolved
    UTC
    Resolved

    GitHub have released all jobs to runners, builds are processing normally.

  • Identified
    UTC
    Identified

    We are currently observing some GitHub Actions jobs waiting to be released by GitHub to their runners. This may indicate an upcoming GitHub outage, or may clear on its own. We will continue to monitor.

Some container builds failing to start
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring

    The fix has deployed, we are monitoring to ensure a full recovery.

  • Identified
    UTC
    Identified

    We have identified a failing service preventing builder machines from acquiring disks and are deploying a fix.

  • Investigating
    UTC
    Investigating

    We are currently investigating reports of some container builds failing to acquire build machines.

Increased queue time for some GitHub Actions jobs
  • Resolved
    UTC
    Resolved

    All jobs are processing normally.

  • Identified
    UTC
    Identified

    We are currently investigating longer queue times for some GitHub Actions jobs - these jobs appear to be waiting longer than expected for the GitHub Actions backend to release them to online runners. We will continue to monitor.

GitHub is investigating degraded Actions performance.
  • Resolved
    UTC
    Resolved

    Queue times appear back to normal now.

  • Monitoring
    UTC
    Monitoring

    GitHub has resolved the issue. We will continue to monitor before we also resolve.

  • Investigating
    UTC
    Investigating

    We are seeing checkouts receiving 500 errors.

    Here is GitHub's current status for the issue: https://www.githubstatus.com/incidents/qd96yfgvmcf9

Jan 2025 to Mar 2025

Next