GitHub: We are investigating reports of degraded performance.
Timeline of updates
- resolved
On December 26, 2023, GitHub received a report through our Bug Bounty Program demonstrating a vulnerability which, if exploited, allowed access to credentials within a production container. We fixed this vulnerability on GitHub.com the same day and began rotating all potentially exposed credentials. Through this process we found some flaws in how we rotate certain credentials and are working on improving our credential rotation process. More detail can be found on our blog: https://github.blog/2024-01-16-rotating-credentials-for-github-com-and-new-ghes-patches/ (opens in new tab)
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-12-29 01:41 UTC, resolved after 23 min, 1 update(s).
- Title
- We are investigating reports of degraded performance.
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/1h37j1mb9xnx
GitHub profileRecent GitHub incidentsAll outages on December 29, 2023GitHub in December 2023MarkdownJSON