Incident with Pages

Summary

Incident with Pages

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.<br /><br />We mitigated the incident by scaling up Pages deployment workers and provisioning additional storage capacity to clear the backlog.<br /><br />GitHub is reviewing capacity planning and autoscaling measures to reduce the likelihood of similar delays in the future.

• Started

  Jul 2, 2026 · 4:54 PM

• Resolved

  Jul 2, 2026 · 6:25 PM

• Duration

  1h 31m

• Severity

  Minor

• ◐

  Investigating

  Jul 2 · 4:54 PM GitHub

  We are investigating reports of degraded performance for Pages

• ◐

  Investigating

  Jul 2 · 4:56 PM GitHub

  We are investigating reports of slow and failing Pages deployments. Access to Pages is unaffected.

• ◐

  Investigating

  Jul 2 · 5:57 PM GitHub

  Pages deployment latency is recovering. The team continues working toward full mitigation and a return to nominal state.

• ✓

  Resolved

  Jul 2 · 6:25 PM GitHub

  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.<br /><br />We mitigated the incident by scaling up Pages deployment workers and provisioning additional storage capacity to clear the backlog.<br /><br />GitHub is reviewing capacity planning and autoscaling measures to reduce the likelihood of similar delays in the future.