Skip to content
Back to GitHubIncident Postmortem
GitHub logo

GitHub

Tracked by PulseWatch

Auto-drafted postmortem

GitHub outage on May 5 — 5h 56m disruption

May 5, 01:51 PM → May 5, 07:48 PM · 5h 56m · high

On May 5, 2026, GitHub experienced a service disruption, which was detected through user reports. The incident began at approximately 13:51 UTC and was resolved by 19:48 UTC on the same day.

Peak reports
20
in 15 min
Total reports
243
during the incident
Duration
5h 56m
tracked by PulseWatch

Impact

Users reported experiencing issues with GitHub, leading to a total of 243 reports during the incident. The primary reported issue types included slow or unresponsive service, accounting for 120 reports, and the website being down, with 118 reports. A small number of users also reported security-related issues. No specific top impacted regions were recorded during this period.

Top reported issues

  • Slow / unresponsive120
  • Website down118
  • Security issue5

Incident timeline

  1. May 5, 01:51 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 5, 01:53 PM

    Status updated: possible issue

  3. May 5, 01:58 PM

    Status updated: possible issue

  4. May 5, 02:08 PM

    Status updated: possible issue

  5. May 5, 02:13 PM

    Status updated: possible issue

  6. May 5, 02:23 PM

    Status updated: possible issue

  7. May 5, 02:28 PM

    Status updated: major issue

  8. May 5, 05:15 PM

    Peak of 19 reports in 15 minutes (baseline 2.0)

  9. May 5, 07:48 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 5, 01:51 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