ARCHIVED OFFICIAL INCIDENT

Actions Job Delays

GitHub · Last saved provider status: resolved

Current service report →
This is historical evidence.

The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.

Saved event details

Provider status
resolved
Provider impact
minor
Provider record created
01 Oct 2026, 14:47:48 UTC
Provider record updated
01 Oct 2026, 17:56:54 UTC
Explicit provider start
01 Oct 2026, 14:47:48 UTC
Explicit provider end
01 Oct 2026, 17:56:54 UTC

Affected components reported by the provider

  • Actions br0l2tvcx85d

These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.

A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.

Provider updates in saved revisions

Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.

  1. resolved

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  2. investigating

    GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  3. investigating

    We are currently applying a mitigation and anticipate recovery within thirty minutes.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  4. investigating

    We have identified an issue with our upstream provider which is causing Actions requests to 429 which is creating the delays. We have escalated to the owning team and are investigating how to mitigate the 429s.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  5. investigating

    We are seeing a reoccurrence in run-start delays, and are continuing to investigate to issue. Customers will potentially experience delays of up to ten minutes.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  6. investigating

    Actions is experiencing degraded performance. We are continuing to investigate.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  7. monitoring

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  8. investigating

    Run-start delays on Ubuntu runners have been resolved. We are investigating run-start delays on Windows runners and will share more information as it becomes available.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  9. investigating

    We have identified the cause of increased Actions run start delays on Ubuntu runners and are actively deploying a fix. Customers may continue to experience intermittent delays while the mitigation rolls out and service metrics return to normal.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  10. investigating

    We are investigating reports of degraded performance for Actions

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC