Skip to main content
HostTracker
HOST-TRACKER
website monitoring service
Status pages Instant check Price
Login Register

GitHub outage on September 1, 2026: Delays in commit processing

GitHub reported an incident affecting GitHub for 1 hour 1 minute on 1 September 2026, from 15:00 to 16:01 UTC.

github.com All times UTC

Resolved

Official incident reported by GitHub

Started
15:00
1 Sep 2026 UTC
Resolved
16:01
1 Sep 2026 UTC
Duration
1h 1m
1 hour 1 minute
Impact
Minor
as rated by GitHub
Updates
4
posted by GitHub

Timeline

All times UTC.

Official incident from GitHub

Delays in commit processing

Resolved Minor impact 1 Sep 2026 15:00 UTC View on GitHub's status page
  1. Official
    Investigating

    We are investigating reports of degraded performance for Pull Requests

  2. Official
    Investigating

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

  3. Official
    Investigating

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

  4. Official
    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. 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...

"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.

All GitHub incidents Live GitHub status Every service we track

Does your product depend on GitHub?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.