← Back to GitHub History
minor✓ Resolved

Incident with Pages - Deployment Lag

GitHub•
Status
resolved
Duration
1h 19m
Updates
3
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
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. <br /><br />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. <br /><br />Customer impact occurred from 11:34 to 15:32 UTC. During this period, we failed to process approximately 128,000 deployments. <br /><br />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.
monitoring
The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
investigating
We are investigating reports of degraded performance for Pages

📊 TECHNICAL DETAILS

Internal ID
6ac6065f-7ac2-49fc-85d5-4607f86aa449
External ID
1xqvzyv99skw
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
1h 19m
Total Duration
3
Status Updates
Affected Components
Pages
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed