Delays in commit processing
At a glance · GitHub's status
ResolvedLasted 1 h
- First posted
- on GitHub Status
- Ended
- · marked resolved
- Affects
- GitHub pull requests
- Edited
- Not since we first saw it
- Source
- GitHub Status · checked just now
In short
GitHub reported degraded service affecting GitHub pull requests, starting 15:00 UTC on 1 Sep. GitHub marked it resolved at 16:01 UTC after 1 h.
GitHub says
GitHub's latest update, , in short excerpts.
On September 1, 2026, between approximately 14:01 and 16:01 UTC, updates in response to pushes were delayed, temporarily showing stale diffs.
Timeline
Times in UTC, GitHub's own where it gives them.
1 Sep
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+1 h 1 min
GitHubResolved
What GitHub changed
GitHub adds updates to its incidents. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full text is on GitHub's page.
One version so far. If GitHub edits it, each change shows here with what was removed and added.
First version we captured ·
As first seen: resolved · 1 service
- Status
- resolved
- Services
- GitHub pull requests
Seen by us · GitHub's timestamp · GitHub's page
Affected services
Official updates
Posted by GitHub Status, newest first. The newest are quoted in their first sentence; the full text of each is on GitHub's page.
Resolved ·
On September 1, 2026, between approximately 14:01 and 16:01 UTC, updates in response to pushes were delayed, temporarily showing stale diffs.
Investigating ·
Time to update pull request diffs have improved to normal thresholds.
Investigating ·
Diffs in the PR view may be stale for several minutes.
Investigating ·
We are investigating reports of degraded performance for Pull Requests
Last updated