GitHub outage on Sep 1, 2026: delays in commit processing

Reports during the incident

Every 15 minutes, 14:00 UTC to 17:15 UTC. Grey: normal. Red line: official incident.

14:00 UTC15:00 UTC16:01 UTC17:15 UTC

What people reported

0 reports during the incident

No reports in this window.

GitHub's updates

Quoted from www.githubstatus.com

15:00 UTC
Investigating
We are investigating reports of degraded performance for Pull Requests
15:00 UTC
Investigating
Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources.
16:00 UTC
Investigating
Time to update pull request diffs have improved to normal thresholds.
16:01 UTC
Resolved
On September 1, 2026, between approximately 14:01 and 16:01 UTC, updates in response to pushes were delayed, temporarily showing stale diffs. The median time to refresh a diff after a push rose from the normal level of about 3 seconds to over 2 minutes at the peak, and more than 140,000 customer accounts had at least one delayed refresh during the most affected 75 minutes. Pushing commits and opening pull requests continued to work normally. The incident was caused by a sharp, concentrated surge in push volume that saturated worker pools and job queueing infrastructure. Autoscaling did not increase capacity as intended, so the backlog did not clear on its own. <br /><br />The incident was mitigated by manually scaling the affected worker pools and increasing push-processing capacity. This allowed the system to process the backlog, after which refresh times returned to normal. To reduce the likelihood and impact of similar incidents, we are adding quotas and throttling earlier in the push path so a single concentrated source of load cannot saturate shared capacity, improving worker-pool autoscaling so capacity is added automatically, and improving monitors for background job process…

Other GitHub incidents

Nov 8

1 h 57 minIncrease in timeouts for some unauthenticated users Details

Nov 5

45 minDegraded performance for multiple GitHub services Details

Nov 5

52 minIncident with Actions Details

All GitHub incidents

Other agents

Know the moment it's back.

Coral shows it in your Mac's notch, and tells you which agent needs you. Free.

Get Coral for Mac

GitHub's updates

15:00 UTC

Investigating

We are investigating reports of degraded performance for Pull Requests

15:00 UTC

Investigating

Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources.

16:00 UTC

Investigating

Time to update pull request diffs have improved to normal thresholds.

16:01 UTC

Resolved

On September 1, 2026, between approximately 14:01 and 16:01 UTC, updates in response to pushes were delayed, temporarily showing stale diffs. The median time to refresh a diff after a push rose from the normal level of about 3 seconds to over 2 minutes at the peak, and more than 140,000 customer accounts had at least one delayed refresh during the most affected 75 minutes. Pushing commits and opening pull requests continued to work normally. The incident was caused by a sharp, concentrated surge in push volume that saturated worker pools and job queueing infrastructure. Autoscaling did not increase capacity as intended, so the backlog did not clear on its own. <br /><br />The incident was mitigated by manually scaling the affected worker pools and increasing push-processing capacity. This allowed the system to process the backlog, after which refresh times returned to normal. To reduce the likelihood and impact of similar incidents, we are adding quotas and throttling earlier in the push path so a single concentrated source of load cannot saturate shared capacity, improving worker-pool autoscaling so capacity is added automatically, and improving monitors for background job process…