← Live dashboard

Delays in commit processing

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Sep 1, 2026, 03:00 PM · Resolved Sep 1, 2026, 04:01 PM

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

GitHub live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with GitHub now? Check the current status

Affected services

Pull Requests

Updates (4)

  1. Sep 1, 2026, 04:01 PM
    Delays in commit processing

    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 inc

    GitHub ↗
  2. Sep 1, 2026, 04:00 PM
    Delays in commit processing

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

    GitHub ↗
  3. Sep 1, 2026, 03:00 PM
    Delays in commit processing

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

    GitHub ↗
  4. Sep 1, 2026, 03:00 PM
    Delays in commit processing

    We are investigating reports of degraded performance for Pull Requests

    GitHub ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow GitHub's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.