GitHub: Incident with Issues, API Requests and Pull Requests
Timeline of updates
- resolved
Between July 28, 2025, 22:23:00 UTC and July 29, 2025 02:06:00 UTC, GitHub experienced degraded performance across multiple services including API, Issues, GraphQL and Pull Requests. During this time, approximately 4% of Web and API requests resulted in 500 errors. This incident was caused by DNS resolution failure while decommissioning infrastructure hosts. We resolved the incident by removing references to the stale hosts. We are working to improve our host replacement process by correcting our automatic host ejection behavior and by ensuring configuration is updated before hosts are decommissioned. This will prevent similar issues 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-07-28 22:40 UTC, resolved after 3.4 h, 1 update(s).
- Title
- Incident with Issues, API Requests and Pull Requests
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/61btx2g21zc6
GitHub profileRecent GitHub incidentsAll outages on July 28, 2025GitHub in July 2025MarkdownJSON