GitHub outage on April 30 106d 1h disruption
Apr 30, 05:30 AM → Aug 14, 07:00 AM · 106d 1h · medium
GitHub experienced a service outage that was detected by automated monitoring signals. The incident began on April 30, 2026, and resulted in a disruption lasting 106 days and 1 hour. Service was fully restored on August 14, 2026.
Impact
During the 106-day and 1-hour incident, GitHub experienced a medium-severity service disruption. This outage was identified through automated monitoring and vendor status page signals. No user-reported data, including affected regions or specific issue types, was collected for this incident.
Incident timeline
- Apr 30, 05:30 AM
PulseWatch detected the incident from automated vendor and probe signals (medium severity)
- Apr 30, 05:53 AM
Status updated: major issue
- Apr 30, 06:08 AM
Status updated: possible issue
- Apr 30, 06:23 AM
Status updated: major issue
- Apr 30, 06:38 AM
Status updated: possible issue
- Aug 14, 07:00 AM
Signals cleared — incident resolved
Official updates
- Apr 30, 05:30 AM
GitHub status page acknowledged the incident.
View official source - Aug 14, 07:00 AM
Slow / unresponsive clustered from 3 sources across 22 signals. Suppressed 21 redundant alerts and flagged flapping behavior. AI confidence: High confidence due to intelligent grouping of multiple correlated signals (22 signals, 21 suppressed), indicating a widespread issue and effective noise reduction. Flapping behavior noted. AI review: likely_real Impact forecast: Moderate disruption to GitHub performance, potentially affecting user experience and repository access.
- Aug 14, 07:00 AM
Root cause: Widespread slow/unresponsive issues on GitHub, potentially due to a core service problem or flapping behavior.