Skip to main content
GitHub

Incident with Pages - Deployment Lag

Degraded Lasted 1h 19m · started · GitHub's page

Level
confirmed
Worst impact
Degraded
Components
Pages
Regions
us
Down Index
22of 100

What to do

  • Check whether you use GitHub Pages in us. 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 19m it lasted.

    Anything that failed between 2026-08-06 15:03 UTC and 2026-08-06 16:22 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 3

  1. investigating

    We are investigating reports of degraded performance for Pages

    provider

  2. monitoring

    The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.

    provider

  3. resolved

    On August 6, 2026, at 07:00 UTC, a configuration change inadvertently reduced the capacity of the service that processes GitHub Pages deployments. As traffic increased over the following hours, latency in the deployment pipeline progressively increased. At 12:09 UTC, latency crossed the alerting threshold and the team began investigating. We reverted the invalid configuration and applied additional mitigations, including reducing status deployment processing to lower the load on our Redis cluster. Latency returned to normal levels at 15:40 UTC. Customer impact occurred from 11:34 to 15:32 UTC. During this period, we failed to process approximately 128,000 deployments. We have updated our alerts to detect elevated processing latency sooner and to notify us immediately when latency causes deployment processing failures. We've confirmed this incident was not fully captured by our availability metrics. In the coming days, we'll update how GitHub Pages availability is measured so incidents like this are accurately reflected going forward.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-8419ee5b51

Is GitHub still down?

No, this incident was resolved 2026-08-06 16:22 UTC. For GitHub's live state, see https://down.guide/github.

How long did it last?

1h 19m, from 2026-08-06 15:03 UTC to 2026-08-06 16:22 UTC, by the times GitHub posted.

What was affected?

GitHub named Pages in us.

What caused it?

GitHub hasn't published a root cause. If it does, it shows here.

Where does this come from?

GitHub's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.