Skip to content
Back to GitHub ActionsIncident Postmortem
GitHub Actions logo

GitHub Actions

Tracked by PulseWatch

Auto-drafted postmortem

GitHub Actions outage on May 4 — 1h 2m disruption

May 4, 04:00 PM → May 4, 05:03 PM · 1h 2m · high

On May 4, 2026, GitHub Actions experienced a service disruption. This outage was initially detected through user reports. The issue was fully resolved by 17:03 UTC on the same day.

Peak reports
19
in 15 min
Total reports
36
during the incident
Duration
1h 2m
tracked by PulseWatch

Impact

Users reported a range of issues during the incident, with the most common being slow or unresponsive service, accounting for 24 reports. Additionally, 6 reports indicated API-related problems, and 5 users experienced general service disruption. One report also cited a security issue. No specific regional impact was recorded during this period.

Top reported issues

  • Slow / unresponsive24
  • API issues6
  • Service disruption5
  • Security issue1

Incident timeline

  1. May 4, 04:00 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 04:15 PM

    Peak of 13 reports in 15 minutes (baseline 1.5)

  3. May 4, 04:38 PM

    Status updated: major issue

  4. May 4, 04:43 PM

    Status updated: major issue

  5. May 4, 05:03 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 04:00 PM

    GitHub Actions status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash