glitchmap

GitHub Container Registry

Operational

All checks pass. Checks: 4

Is GitHub Container Registry down? — short answer →

Holding for 12d

Subscribe in Telegram

100.00%
Uptime · 24 hours
100.00%
Uptime · 7 days
99.90%
Uptime · 30 days
801ms
Latency
2026-08-25 — —2026-08-26 — —2026-08-27 — —2026-08-28 — —2026-08-29 — —2026-08-30 — —2026-08-31 — —2026-09-01 — —2026-09-02 — —2026-09-03 — —2026-09-04 — —2026-09-05 — —2026-09-06 — —2026-09-07 — —2026-09-08 — —2026-09-09 — —2026-09-10 — —2026-09-11 — —2026-09-12 — —2026-09-13 — —2026-09-14 — —2026-09-15 — —2026-09-16 — —2026-09-17 — —2026-09-18 — —2026-09-19 — —2026-09-20 — —2026-09-21 — —2026-09-22 — —2026-09-23 — 100.00%2026-09-24 — 100.00%2026-09-25 — 100.00%2026-09-26 — 100.00%2026-09-27 — 100.00%2026-09-28 — 100.00%2026-09-29 — 100.00%2026-09-30 — 100.00%2026-10-01 — 100.00%2026-10-02 — 100.00%2026-10-03 — 100.00%2026-10-04 — 100.00%2026-10-05 — 100.00%2026-10-06 — 100.00%2026-10-07 — 100.00%2026-10-08 — 100.00%2026-10-09 — 100.00%2026-10-10 — 100.00%2026-10-11 — 100.00%2026-10-12 — 100.00%2026-10-13 — 100.00%2026-10-14 — 100.00%2026-10-15 — 100.00%2026-10-16 — 100.00%2026-10-17 — 100.00%2026-10-18 — 100.00%2026-10-19 — 100.00%2026-10-20 — 100.00%2026-10-21 — 100.00%2026-10-22 — 100.00%2026-10-23 — 100.00%2026-10-24 — 100.00%2026-10-25 — 100.00%2026-10-26 — 100.00%2026-10-27 — 100.00%2026-10-28 — 100.00%2026-10-29 — 100.00%2026-10-30 — 100.00%2026-10-31 — 100.00%2026-11-01 — 100.00%2026-11-02 — 100.00%2026-11-03 — 100.00%2026-11-04 — 100.00%2026-11-05 — 100.00%2026-11-06 — 100.00%2026-11-07 — 100.00%2026-11-08 — 96.90%2026-11-09 — 99.00%2026-11-10 — 100.00%2026-11-11 — 100.00%2026-11-12 — 100.00%2026-11-13 — 100.00%2026-11-14 — 100.00%2026-11-15 — 100.00%2026-11-16 — 100.00%2026-11-17 — 100.00%2026-11-18 — 100.00%2026-11-19 — 100.00%2026-11-20 — 100.00%2026-11-21 — 100.00%2026-11-22 — 100.00%
Last 90 days today
100%
Availability and latency. Hover for exact values.

Checks

4
api Website / API Passing
dns DNS Passing
tls TLS certificate Passing
web Website / API Passing

Not working for you?

Tell us what exactly is broken. Reports are counted separately from our own checks and do not change the status on this page.

Incident history

14
Degraded Checks failing: 1 of 4 — web 09.11 07:36 · 40m Degraded Checks failing: 1 of 4 — web 09.11 07:24 · 9m Degraded Checks failing: 1 of 4 — web 09.11 05:17 · 1h 12m Degraded Checks failing: 1 of 4 — web 08.11 11:50 · 2m Degraded Checks failing: 1 of 4 — web 08.11 11:01 · 1m Degraded Checks failing: 1 of 4 — web 08.11 08:46 · 2h 8m Degraded Checks failing: 1 of 4 — web 05.11 14:37 · 3m Degraded Checks failing: 1 of 4 — web 05.11 14:12 · 1m Degraded Checks failing: 1 of 4 — web 05.11 09:15 · 3m Degraded Checks failing: 1 of 4 — web 10.10 23:43 · 3m Degraded Checks failing: 1 of 4 — web 10.10 23:31 · 5m Degraded Checks failing: 1 of 4 — web 09.10 06:33 · 3m Degraded Checks failing: 1 of 4 — web 09.10 06:26 · 3m Degraded Checks failing: 1 of 4 — web 09.10 06:09 · 12m

Measurements and sources

glitchmap checks public service endpoints and uses official status reports when available. A passing check confirms that endpoint only; it does not test every feature or your connection.

How we check