glitchmap

Akamai Linode

Operational

All checks pass. Checks: 4 · Vendor incidents: 2

Is Akamai Linode down? — short answer →

Holding for 1d

Subscribe in Telegram

100.00%
Uptime · 24 hours
100.00%
Uptime · 7 days
99.90%
Uptime · 30 days
1162ms
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 — 97.90%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

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

13
Degraded Status raised from the vendor's official page 20.11 08:30 · 1h 45m Degraded Status raised from the vendor's official page 17.11 22:10 · 30m Degraded Status raised from the vendor's official page 05.11 13:01 · 4h 24m Degraded Status raised from the vendor's official page 02.11 18:06 · 2h 50m Degraded Status raised from the vendor's official page 31.10 17:51 · 2d Degraded Checks failing: 1 of 4 — api 28.10 03:57 · 5h 24m Degraded Status raised from the vendor's official page 25.10 13:56 · 2h 20m Degraded Status raised from the vendor's official page 20.10 20:11 · 1h 34m Degraded Status raised from the vendor's official page 20.10 12:32 · 7h 34m Degraded Status raised from the vendor's official page 09.10 03:46 · 1h 39m Degraded Status raised from the vendor's official page 02.10 19:14 · 1h 4m Degraded Status raised from the vendor's official page 02.10 16:09 · 3h 1m Degraded Status raised from the vendor's official page 25.09 15:11 · 1h 14m

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

Service Issue - Linode Kubernetes Engine monitoring 20.11 08:27
Service Issue - Block Storage (BR-GRU) monitoring 28.10 20:17

Incident titles come from the vendor and are shown as published