Operational GitHub status
github.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread GitHub problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS36459: routing data not loaded on this view
- News & network weather no recent mentions
- Providers it may run on (inferred) Microsoft Azure: no issues
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Webhooks, Pull Requests, Actions
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 30 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Delays for Pull Requests and Webhook deliveries”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside GitHub's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
GitHub may run on Microsoft Azure (inferred). 2 other services in our catalog may lean on GitHub, so trouble here can show up elsewhere first. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on GitHub or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers GitHub may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with GitHub. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Delays for Pull Requests and Webhook deliveries
critical resolved · started · resolved
15 updates
- investigating
We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks
- investigating
Actions is experiencing degraded performance. We are continuing to investigate.
- investigating
We are investigating delays affecting pull request updates and webhook deliveries. Increased load on our event streaming platform is contributing to hotspots. We are shifting traffic away from affected areas and adding processing capacity; impact is ongoing while these mitigations take effect.
- investigating
We continue to see delays affecting pull request updates, webhook deliveries, and audit log events. The event streaming platform is showing signs of recovery, and we are monitoring as the impact continues.
- investigating
Audit log events and Actions workflow status updates continue to be delayed. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring the recovery and will share further updates as we learn more.
- investigating
Audit log events are delayed by up to 100 minutes, and Actions workflow status updates continue to experience extended delays. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring recovery and will share further updates as we learn more.
- investigating
Pull Requests is operating normally.
- investigating
Audit log events continue to be delayed by up to 110 minutes. Pull request updates have recovered. Actions is recovering, and users should no longer experience impact in Actions. Webhook deliveries continue to recover as we work through backlogs. We are monitoring recovery and will share further updates as we learn more.
- investigating
Actions and Webhooks are operating normally.
- investigating
Actions and webhook deliveries have recovered. Audit log events are still delayed by about 100 minutes. We are working through the backlog, and full recovery will take some time. We will share more updates as recovery continues.
- investigating
Pull request updates, Actions, and webhook deliveries have recovered. Audit log events are recovering and delays are decreasing, but we expect the remaining backlog to take approximately two to three hours to clear. We’re monitoring recovery and will share further updates.
- investigating
Audit log events are recovering, with delays now below 90 minutes as the remaining backlog is processed. We’ve reduced load on the event-streaming platform and are monitoring recovery. Further updates will follow.
- investigating
Audit log events continue to recover, with delays now below 70 minutes. We’ve applied mitigations to speed recovery and expect audit logs to fully recover in about 40 minutes. Pull request updates, Actions, and webhook deliveries remain recovered. We are monitoring progress and will share further updates.
- investigating
Pull request updates, Actions, and webhook deliveries have recovered. Audit log delays are now below 40 minutes, within the healthy threshold, and continue to decrease as the remaining backlog is processed.
- resolved
On October 21, 2026, between 13:22 UTC and 19:22 UTC, several GitHub services were delayed due to degradation of our internal event streaming platform. <br /><br />Pull request updates, push webhooks, and push-triggered Actions workflows were delayed by up to 33 minutes until 15:36 UTC. Actions status updates were delayed by up to 33 minutes until 16:16 UTC, holding up some merges and deployments that wait on checks. Webhook deliveries and live updates were delayed by up to 25 minutes until 16:52 UTC. Audit log events were delayed by up to two hours. <br /><br />This was due to servers in the platform running out of memory caused by client reconnections without sufficient retry backoff. We mitigated the incident by moving the busiest workloads to less-loaded servers and adding capacity. <br /><br />We have since added reconnection backoff and added server capacity. We are building a solu
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.