GlobalOutageMap
← Live dashboard
GitHub logoGitHub

Incident with Actions

ResolvedcriticalOfficial source confirmedSpecific component onlyFirst recorded update Aug 26, 2026, 03:11 PM · Resolved Aug 26, 2026, 06:01 PM

On August 26, 2026 from 15:02 to 15:45 UTC, Actions jobs failed to start. The following 2 hours until 17:40 UTC, Actions runs were delayed starting by more than 5 minutes as the system caught up with delayed load. This impact was triggered by saturation of writes to the database primary used by the service processing triggers for Actions workflows. The primary was failed over, but the system did not fully recover. The saturation was caused by growing daily peak load combined with an upstream issue in GitHub’s event processing infrastructure,...

GitHub live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with GitHub now? Check the current status

Affected services

ActionsPages

Updates (11)

  1. Aug 26, 2026, 06:01 PM
    Incident with Actions

    On August 26, 2026 from 15:02 to 15:45 UTC, Actions jobs failed to start. The following 2 hours until 17:40 UTC, Actions runs were delayed starting by more than 5 minutes as the system caught up with delayed load. This impact was triggered by saturation of writes to the database primary used by the service processing triggers for Actions workflows. The primary was failed over, but the system did not fully recover. The saturation was caused by growing daily peak load combined with an upstream issue in GitHub’s event processing infrastructure, https://www.githubstatus.com/incidents/hcbtzksccj2f,

    GitHub ↗
  2. Aug 26, 2026, 06:00 PM
    Incident with Actions

    All inbound queues have recovered and Actions is operating as expected. 3.7% of jobs assigned to larger runners during the early stage of this incident are stuck waiting for runner assignment. Those will be canceled within the hour. Other runners are successfully processing all new jobs.

    GitHub ↗
  3. Aug 26, 2026, 05:54 PM
    Incident with Actions

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

    GitHub ↗
  4. Aug 26, 2026, 05:32 PM
    Incident with Actions

    We are continuing to observe recovery and expect actions inbound queues to be back to normal in <30min. Work will continue to flow through the system subject to per-customer concurrency limits.

    GitHub ↗
  5. Aug 26, 2026, 04:50 PM
    Incident with Actions

    We are continuing to observe recovery and delayed queues are burning down. Some customers will continue to see increased delays until all throttled work has been completed - we expect this within the next hour.

    GitHub ↗
  6. Aug 26, 2026, 04:49 PM
    Incident with Actions

    Pages is operating normally.

    GitHub ↗
  7. Aug 26, 2026, 04:14 PM
    Incident with Actions

    We believe we've identified and addressed the issue and are ramping traffic back up slowly to ensure it doesn't recur. Some customers will continue to see delays as we ramp up.

    GitHub ↗
  8. Aug 26, 2026, 03:48 PM
    Incident with Actions

    primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues

    GitHub ↗
  9. Aug 26, 2026, 03:23 PM
    Incident with Actions

    We've identified an issue with a database primary and are failing over to a replica immediately

    GitHub ↗
  10. Aug 26, 2026, 03:12 PM
    Incident with Actions

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

    GitHub ↗
  11. Aug 26, 2026, 03:11 PM
    Incident with Actions

    We are investigating reports of degraded availability for Actions

    GitHub ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow GitHub's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.