Skip to content
Back to GitHubIncident Postmortem
GitHub logo

GitHub

Tracked by PulseWatch

Auto-drafted postmortem

GitHub outage on May 4 1h 32m disruption

May 4, 04:00 PM → May 4, 05:33 PM · 1h 32m · medium

On May 4, 2026, GitHub experienced a service disruption, detected through user reports. The incident began at approximately 16:00 UTC and was resolved by 17:33 UTC on the same day.

Peak reports
25
in 15 min
Total reports
91
during the incident
Duration
1h 32m
tracked by PulseWatch

Impact

During the 1 hour and 32 minute disruption, a total of 91 user reports were received, indicating a widespread impact. The primary issues reported by users were related to the GitHub website being down, accounting for 66 reports, and slow or unresponsive service, with 24 reports. A single report also indicated a security issue. No specific top impacted regions were identified during this incident.

Top reported issues

  • Website down66
  • Slow / unresponsive24
  • Security issue1

Incident timeline

  1. May 4, 04:00 PM

    PulseWatch detected elevated report volume (medium severity)

  2. May 4, 04:33 PM

    Status updated: possible issue

  3. May 4, 04:38 PM

    Status updated: major issue

  4. May 4, 04:43 PM

    Status updated: major issue

  5. May 4, 04:45 PM

    Peak of 25 reports in 15 minutes (baseline 2.0)

  6. May 4, 04:48 PM

    Status updated: major issue

  7. May 4, 04:53 PM

    Status updated: major issue

  8. May 4, 04:58 PM

    Status updated: major issue

  9. May 4, 05:03 PM

    Status updated: possible issue

  10. May 4, 05:08 PM

    Status updated: possible issue

  11. May 4, 05:13 PM

    Status updated: possible issue

  12. May 4, 05:33 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 04:00 PM

    GitHub 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