Incident with Pages
Incident
Report for GitHub
Resolved
On March 20, 2025, between 19:24 UTC and 20:42 UTC the GitHub Pages experience was degraded and returned 503s for some customers. We saw an error rate of roughly 2% for Pages views, and new page builds were unable to complete successfully before timing out.
This was due to replication failure at the database layer between a write destination and read destination. We mitigated the incident by redirecting reads to the same destination as writes.
The error with replication occurred while in this transitory phase, as we are in the process of migrating the underlying data for Pages to new database infrastructure. Additionally our monitors failed to detect the error.
We are addressing the underlying cause of the failed replication and telemetry.
This was due to replication failure at the database layer between a write destination and read destination. We mitigated the incident by redirecting reads to the same destination as writes.
The error with replication occurred while in this transitory phase, as we are in the process of migrating the underlying data for Pages to new database infrastructure. Additionally our monitors failed to detect the error.
We are addressing the underlying cause of the failed replication and telemetry.
Update
We have resolved the issue for Pages. If you're still experiencing issues with your GitHub Pages site, please rebuild.
Update
Customers may not be able to create or make changes to their GitHub Pages sites. Customers who rely on webhook events from Pages builds might also experience a downgraded experience.
Update
Webhooks is experiencing degraded performance. We are continuing to investigate.
Investigating
We are investigating reports of degraded performance for Pages
This incident affected: Webhooks and Pages.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe