GitHub Availability Report: November 2024
In November, we experienced one incident that resulted in degraded performance across GitHub services.
In November, we experienced one incident that resulted in degraded performance across GitHub services.
November 19 10:56 UTC (lasting 1 hour and 7 minutes)
On November 19, 2024, between 10:56:00 UTC and 12:03:00 UTC, the notifications service was degraded and stopped sending notifications to all our dotcom customers. On average, notification delivery was delayed by about one hour. This was due to a database host coming out of a regular maintenance process in read-only mode.
We mitigated the incident by making the host writable again. Following this, notification delivery recovered, and any delivery jobs that had failed during the incident were successfully retried. All notifications were fully recovered and available to users by 12:36 UTC.
To prevent similar incidents moving forward, we are working to improve our observability across database clusters to reduce our time to detection and improve our system resilience on startup.
Please follow our status page for real-time updates on status changes and post-incident recaps. To learn more about what we’re working on, check out the GitHub Engineering Blog.
Tags:
Written by
Related posts
GitHub Universe 2026: Evolving every layer of the stack
Today, we laid out our vision for GitHub as the most comprehensive, end-to-end software delivery system in the world.
Octoverse: Commits, pushes, reach new highs in 2026 as developers build with agents
See how a record year of growth reached every industry, every field, and every kind of builder in the 2026 Octoverse report.
The next developer interface is ambient intelligence
AI, agents, voice, and physical controls are shifting software development from operating tools to expressing intent—and helping developers stay focused on building.