GitHub: Incident with Pages
Timeline of updates
- resolved
On July 2nd, 2026, between approximately 15:00 and 18:30 UTC, the GitHub Pages service experienced degraded deployment performance due to a surge in demand that exceeded available processing capacity. During this period, users publishing to GitHub Pages may have seen their deployments queued or taking substantially longer than usual to go live. No other GitHub services were impacted. We mitigated the incident by scaling up Pages deployment workers and provisioning additional storage capacity to clear the backlog. GitHub is reviewing capacity planning and autoscaling measures to reduce the likelihood of similar delays in the future.
From GitHub’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitHub, started 2026-07-02 16:54 UTC, resolved after 1.5 h, 1 update(s).
- Title
- Incident with Pages
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/5bnwwg9tzd4q
GitHub profileRecent GitHub incidentsAll outages on July 2, 2026GitHub in July 2026MarkdownJSON