Delays in commit processing
GitHub · Last saved provider status: resolved
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- resolved
- Provider impact
- minor
- Provider record created
- 01 Sep 2026, 15:00:22 UTC
- Provider record updated
- 09 Sep 2026, 19:29:52 UTC
- Explicit provider start
- 01 Sep 2026, 15:00:22 UTC
- Explicit provider end
- 01 Sep 2026, 16:01:21 UTC
Affected components reported by the provider
- Pull Requests
hhtssxt0f5v2
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- 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 processing so on-call is paged before customers experience delayed pull request updates.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
Time to update pull request diffs have improved to normal thresholds.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of degraded performance for Pull Requests
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC