GitHub: Incident with Pull Requests
Timeline of updates
- resolved
On October 9, 2023 at 14:24 UTC, a noticeable delay in commits appearing in pull requests was detected. During the incident, approximately 9% of pull requests (less than the 20% first reported) experienced staleness of up to 7m. The root cause was identified to be an increase in the latency of a downstream dependency causing pull request workers to saturate their available capacity, resulting in delayed updates to PRs - no data was lost during this incident. We mitigated this by adding additional capacity to the affected worker pool at 15:02 UTC. This allowed our background jobs to catch up with the backlog of updates and provide relief to our customers. Additionally, we have significantly increased the performance of the downstream service to prevent recurrence
From GitHub’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitHub, started 2023-10-09 14:51 UTC, resolved after 27 min, 1 update(s).
- Title
- Incident with Pull Requests
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/gtsz1l2jc96n
GitHub profileRecent GitHub incidentsAll outages on October 9, 2023GitHub in October 2023MarkdownJSON