GitHub: Degraded REST API success rates for some customers
Timeline of updates
- resolved
On September 4, 2025 between 15:30 UTC and 20:00 UTC the REST API endpoints git/refs, git/refs/, and git/matching-refs/ were degraded and returned elevated errors for repositories with reference counts over 22k. On average, the request error rate to these specific endpoints was 0.5%. Overall REST API availability remained 99.9999%. This was due to the introduction of a code change that added latency to reference evaluations and overly affected repositories with many branches, tags, or other references. We mitigated the incident by reverting the new code. We are working to improve performance testing and to reduce our time to detection and mitigation of issues like this one in the future.
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 2025-09-04 18:16 UTC, resolved after 2.1 h, 1 update(s).
- Title
- Degraded REST API success rates for some customers
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/mdj41rgqwjx5
GitHub profileRecent GitHub incidentsAll outages on September 4, 2025GitHub in September 2025MarkdownJSON