glitchmap

Snyk

Operational

All checks pass. Checks: 3

Is Snyk down? — short answer →

Holding for 1d

Subscribe in Telegram

100.00%
Uptime · 24 hours
100.00%
Uptime · 7 days
100.00%
Uptime · 30 days
142ms
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 — —2026-09-24 — —2026-09-25 — —2026-09-26 — —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 — 100.00%2026-11-09 — 100.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

3
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

18
Degraded Status raised from the vendor's official page 20.11 16:55 · 1h 49m Degraded Status raised from the vendor's official page 18.11 14:51 · 2h 19m Degraded Status raised from the vendor's official page 15.11 01:08 · 20m Degraded Status raised from the vendor's official page 11.11 20:38 · 14h 15m Degraded Status raised from the vendor's official page 02.11 19:46 · 1h 59m Degraded Status raised from the vendor's official page 29.10 10:46 · 1h 44m Degraded Status raised from the vendor's official page 23.10 14:11 · 1h 10m Degraded Status raised from the vendor's official page 22.10 21:56 · 15h 25m Degraded Status raised from the vendor's official page 20.10 16:36 · 1h 50m Degraded Status raised from the vendor's official page 17.10 01:46 · 50m Degraded Status raised from the vendor's official page 15.10 20:41 · 30m Degraded Status raised from the vendor's official page 13.10 07:36 · 35m Degraded Status raised from the vendor's official page 07.10 19:31 · 17h 29m Degraded Status raised from the vendor's official page 07.10 15:06 · 4h 20m Degraded Status raised from the vendor's official page 06.10 22:56 · 1h 5m Degraded Status raised from the vendor's official page 06.10 14:44 · 3h 21m Degraded Status raised from the vendor's official page 03.10 19:54 · 2d Degraded Status raised from the vendor's official page 28.09 07:53 · 3h 24m

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

Official status page

Operational

Official status data source

No incidents recorded

Incident titles come from the vendor and are shown as published