GitHub Container Registry: SLA evidence report
GitHub Container Registry: SLA evidence report
We only started checking GitHub Container Registry on 2026-11-02, so the window starts there.
We hold no probe record for GitHub Container Registry: we read its status page, so the only incident record here is what GitHub Container Registry declared there. Nothing below is a measurement of ours, and the absence of one is not a record of no downtime.
- Incidents GitHub Container Registry declared
- 8
- On its own status page, in this window.
- Window
- 2026-11-02 to 2026-11-05
- UTC, 3 days.
Nov 2, 2026, 5:46 PM UTC to Nov 2, 2026, 6:24 PM UTC
Elevated errors on GPT-5.4 Nano, impact minor
Nov 3, 2026, 1:25 PM UTC to Nov 3, 2026, 1:56 PM UTC
Incident with API, Git, and Copilot requests, impact minor
Nov 3, 2026, 8:57 PM UTC to Nov 3, 2026, 10:41 PM UTC
Incident with Git Operations, impact minor
Nov 4, 2026, 8:45 AM UTC to Nov 4, 2026, 10:01 AM UTC
Increased task-related errors for Copilot Mission Control, impact minor
Nov 4, 2026, 9:49 AM UTC to Nov 4, 2026, 11:50 AM UTC
Incident with Pull Requests, Git Operations and Issues, impact major
Nov 4, 2026, 4:05 PM UTC to Nov 4, 2026, 5:01 PM UTC
Incident with Actions and Pages, impact major
Nov 4, 2026, 5:40 PM UTC to Nov 4, 2026, 6:16 PM UTC
Incident with Actions, impact major
Nov 5, 2026, 4:50 PM UTC to Nov 5, 2026, 5:42 PM UTC
Incident with Actions, impact minor
Methodology
These incidents come from GitHub Container Registry's own public status feed, polled on our own schedule, and are shown as the vendor wrote them. They are not our measurement, we do not estimate an SLA credit from them, and they are not proof of downtime for your account. The credit GitHub Container Registry owes, if any, is decided under its own SLA.