Skip to content
Back to GitHubIncident Postmortem
GitHub logo

GitHub

Tracked by PulseWatch

Auto-drafted postmortem

GitHub outage on May 5 4h 26m disruption

May 5, 03:11 PM → May 5, 07:38 PM · 4h 26m · medium

GitHub experienced a service disruption on May 5, 2026. This incident was detected via user reports indicating various issues with the platform. The disruption was resolved on May 5, 2026, at 19:38 UTC.

Peak reports
22
in 15 min
Total reports
179
during the incident
Duration
4h 26m
tracked by PulseWatch

Impact

Users reported a range of issues during the GitHub service disruption. The most frequently reported problems included the website being slow or unresponsive, accounting for 92 reports, and the website being completely down, with 85 reports. A small number of users also reported security-related issues. In total, 179 user reports were received during the 4-hour and 26-minute incident, indicating widespread impact across the platform.

Top reported issues

  • Slow / unresponsive92
  • Website down85
  • Security issue2

Incident timeline

  1. May 5, 03:11 PM

    PulseWatch detected elevated report volume (medium severity)

  2. May 5, 03:43 PM

    Status updated: possible issue

  3. May 5, 03:53 PM

    Status updated: possible issue

  4. May 5, 03:58 PM

    Status updated: possible issue

  5. May 5, 04:08 PM

    Status updated: possible issue

  6. May 5, 04:13 PM

    Status updated: possible issue

  7. May 5, 04:23 PM

    Status updated: possible issue

  8. May 5, 04:28 PM

    Status updated: possible issue

  9. May 5, 04:38 PM

    Status updated: possible issue

  10. May 5, 04:43 PM

    Status updated: possible issue

  11. May 5, 04:48 PM

    Status updated: possible issue

  12. May 5, 05:15 PM

    Peak of 19 reports in 15 minutes (baseline 2.0)

  13. May 5, 07:38 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 5, 03:11 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