Incident with Pages

What to do

• Check whether you use GitHub Pages. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 31m it lasted.

  Anything that failed between 2026-07-02 16:54 UTC and 2026-07-02 18:25 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 4

1. investigatingJul 2, 2026, 4:54 PM UTC

   We are investigating reports of degraded performance for Pages

   provider

2. investigatingJul 2, 2026, 4:56 PM UTC

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

   provider

3. investigatingJul 2, 2026, 5:57 PM UTC

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

   provider

4. resolvedJul 2, 2026, 6:25 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.