GitHub delays pull requests, webhooks, and audit logs
First merged summary.
GitHub is still investigating event-streaming hotspots slowing pull request updates, webhooks, and audit log events.
GitHub opened an incident at 14:52 UTC on October 21, 2026, citing degraded performance for Actions, pull requests, and webhooks. Later updates said increased load on the event streaming platform created hotspots. GitHub is shifting traffic and adding capacity. As of 15:58 UTC, delays still affect pull request updates, webhook deliveries, and audit log events, though the platform is showing signs of recovery.
- Incident opened at 14:52 UTC on October 21, 2026.
- Actions degradation was noted at 15:15 UTC.
- GitHub blamed hotspots from event-streaming platform load.
- Mitigations were still taking effect at 15:36 UTC.
- Audit log events were listed as delayed by 15:58 UTC.
- GitHub is shifting traffic and adding capacity.
Timeline
dated events in the reporting · oldest first- Oct 21, 2026GitHub opened an incident at 14:52 UTC. · Hacker News
- Oct 21, 2026Actions degradation noted at 15:15 UTC. · Hacker News
- Oct 21, 2026Mitigations still taking effect at 15:36 UTC. · Hacker News
- Oct 21, 2026Audit log delays listed by 15:58 UTC. · Hacker News
What each outlet adds
beyond the shared facts- Hacker NewsTimed status updates and the event-streaming hotspot cause.
- Vendors
- GitHub
Coverage
oldest first · one row per article · UTCGitHub Actions, Pages, and Webhooks hit by degraded availability
GitHub said customers may see delays in workflow runs, site builds, and webhook delivery while it investigates.
GitHub delays pull requests, webhooks, and Actions
GitHub says event-streaming hotspots are still slowing pull request updates, webhook deliveries, and audit log events.