Skip to content
Back to GitHubIncident Postmortem
GitHub logo

GitHub

Tracked by PulseWatch

Auto-drafted postmortem

GitHub outage on May 5 — 2h 59m disruption

May 5, 04:28 PM → May 5, 07:28 PM · 2h 59m · critical

GitHub experienced a critical service outage on May 5, 2026. The incident began at 16:28:51 UTC and was resolved at 19:28:16 UTC, lasting for 2 hours and 59 minutes. The issue was detected via user reports.

Peak reports
21
in 15 min
Total reports
139
during the incident
Duration
2h 59m
tracked by PulseWatch

Impact

During the incident, users reported that the GitHub website was down and experienced slow or unresponsive performance. A small number of reports also mentioned security issues. The outage was detected through user reports and correlated across multiple monitoring signals, including official vendor communications and social chatter. No specific regions were identified as being disproportionately impacted.

Top reported issues

  • Website down85
  • Slow / unresponsive52
  • Security issue2

Incident timeline

  1. May 5, 04:28 PM

    PulseWatch detected elevated report volume (critical severity)

  2. May 5, 04:53 PM

    Status updated: major issue

  3. May 5, 05:08 PM

    Status updated: possible issue

  4. May 5, 05:13 PM

    Status updated: possible issue

  5. May 5, 05:15 PM

    Peak of 19 reports in 15 minutes (baseline 2.0)

  6. May 5, 05:23 PM

    Status updated: major issue

  7. May 5, 05:28 PM

    Status updated: major issue

  8. May 5, 05:33 PM

    Status updated: possible issue

  9. May 5, 05:38 PM

    Status updated: major issue

  10. May 5, 05:43 PM

    Status updated: major issue

  11. May 5, 05:48 PM

    Status updated: major issue

  12. May 5, 05:54 PM

    Status updated: major issue

  13. May 5, 05:58 PM

    Status updated: major issue

  14. May 5, 07:28 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 5, 04:28 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-lite