Guardian

← All providers · Cloud & Infrastructure

Akamai.

1 service independently monitored by Guardian

GUARDIAN-MEASURED

● OPERATIONALAll systems operational

Our keyless probes, every 5 minutes. Independent of the vendor.

VENDOR-REPORTED

■ ALL SYSTEMS OPERATIONAL

Their status feed, fetched 2m ago. Shown for reference.

Two lanes. Never merged into one number.

Measured by Guardian probes only. Mobile rows show a separately computed trailing 30-day percentage beside the 30 visible cells.

APIs

  • Linode API● OPERATIONAL
    90 days ago99.97 % uptime · grade A · 90 d · 10 changes · last 2026-10-0799.99 % uptime · grade A · 30 d · 10 changes · last 2026-10-07 · 30 dtoday

MCP servers

□ NO DATA · no MCP servers monitored

Vendor-reported components

As self-reported by Akamai’s official status feed, grouped to mirror its status page. Shown for reference. The Guardian-measured statuses and uptime below are probed independently and unaffected by this data.

BackupsOperational31 of 31 operational
  • AP-Northeast-2 (Tokyo 2) BackupsOperational
  • AP-South (Singapore) BackupsOperational
  • AP-Southeast (Sydney) BackupsOperational
  • AP-West (Mumbai) BackupsOperational
  • AU-MEL (Melbourne) BackupsOperational
  • BR-GRU (São Paulo) BackupsOperational
  • CA-Central (Toronto) BackupsOperational
  • DE-FRA-2 (Frankfurt 2) BackupsOperational
  • ES-MAD (Madrid) BackupsOperational
  • EU-Central (Frankfurt) BackupsOperational
  • EU-West (London) BackupsOperational
  • FR-PAR (Paris) BackupsOperational
  • GB-LON (London 2) BackupsOperational
  • ID-CGK (Jakarta) BackupsOperational
  • IN-BOM-2 (Mumbai 2) BackupsOperational
  • IN-MAA (Chennai) BackupsOperational
  • IT-MIL (Milan) BackupsOperational
  • JP-OSA (Osaka) BackupsOperational
  • JP-TYO-3 (Tokyo) BackupsOperational

+12 more components · view all on Akamai’s status page

Block StorageOperational31 of 31 operational
  • AP-Northeast-2 (Tokyo 2) Block StorageOperational
  • AP-South (Singapore) Block StorageOperational
  • AP-Southeast (Sydney) Block StorageOperational
  • AP-West (Mumbai) Block StorageOperational
  • AU-MEL (Melbourne) Block StorageOperational
  • BR-GRU (São Paulo) Block StorageOperational
  • CA-Central (Toronto) Block StorageOperational
  • DE-FRA-2 (Frankfurt 2) Block StorageOperational
  • ES-MAD (Madrid) Block StorageOperational
  • EU-Central (Frankfurt) Block StorageOperational
  • EU-West (London) Block StorageOperational
  • FR-PAR (Paris) Block StorageOperational
  • GB-LON (London 2) Block StorageOperational
  • ID-CGK (Jakarta) Block StorageOperational
  • IN-BOM-2 (Mumbai 2) Block StorageOperational
  • IN-MAA (Chennai) Block StorageOperational
  • IT-MIL (Milan) Block StorageOperational
  • JP-OSA (Osaka) Block StorageOperational
  • JP-TYO-3 (Tokyo 3) Block StorageOperational

+12 more components · view all on Akamai’s status page

Linode Kubernetes EngineOperational31 of 31 operational
  • AP-Northeast (Tokyo 2) Linode Kubernetes EngineOperational
  • AP-South (Singapore) Linode Kubernetes EngineOperational
  • AP-Southeast (Sydney) Linode Kubernetes EngineOperational
  • AP-West (Mumbai) Linode Kubernetes EngineOperational
  • AU-MEL (Melbourne) Linode Kubernetes EngineOperational
  • BR-GRU (São Paulo) Linode Kubernetes EngineOperational
  • CA-Central (Toronto) Linode Kubernetes EngineOperational
  • DE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineOperational
  • ES-MAD (Madrid) Linode Kubernetes EngineOperational
  • EU-Central (Frankfurt) Linode Kubernetes EngineOperational
  • EU-West (London) Linode Kubernetes EngineOperational
  • FR-PAR (Paris) Linode Kubernetes EngineOperational
  • GB-LON (London 2) Linode Kubernetes EngineOperational
  • ID-CGK (Jakarta) Linode Kubernetes EngineOperational
  • IN-BOM-2 (Mumbai 2) Linode Kubernetes EngineOperational
  • IN-MAA (Chennai) Linode Kubernetes EngineOperational
  • IT-MIL (Milan) Linode Kubernetes EngineOperational
  • JP-OSA (Osaka) Linode Kubernetes EngineOperational
  • JP-TYO-3 (Tokyo 3) Linode Kubernetes EngineOperational

+12 more components · view all on Akamai’s status page

NodeBalancersOperational31 of 31 operational
  • AP-Northeast-2 (Tokyo 2) NodeBalancersOperational
  • AP-South (Singapore) NodeBalancersOperational
  • AP-Southeast (Sydney) NodeBalancersOperational
  • AP-West (Mumbai) NodeBalancersOperational
  • AU-MEL (Melbourne) NodeBalancersOperational
  • BR-GRU (São Paulo) NodeBalancersOperational
  • CA-Central (Toronto) NodeBalancersOperational
  • DE-FRA-2 (Frankfurt 2) NodeBalancersOperational
  • ES-MAD (Madrid) NodeBalancersOperational
  • EU-Central (Frankfurt) NodeBalancersOperational
  • EU-West (London) NodeBalancersOperational
  • FR-PAR (Paris) NodeBalancersOperational
  • GB-LON (London 2) NodeBalancersOperational
  • ID-CGK (Jakarta) NodeBalancersOperational
  • IN-BOM-2 (Mumbai 2) NodeBalancersOperational
  • IN-MAA (Chennai) NodeBalancersOperational
  • IT-MIL (Milan) NodeBalancersOperational
  • JP-OSA (Osaka) NodeBalancersOperational
  • JP-TYO-3 (Tokyo 3) NodeBalancersOperational

+12 more components · view all on Akamai’s status page

Object StorageOperational26 of 26 operational
  • AP-South (Singapore) Object StorageOperational
  • AU-MEL (Melbourne)Operational
  • AU-MEL (Melbourne) Object StorageOperational
  • BR-GRU (Sao Paulo) Object StorageOperational
  • DE-FRA-2 (Frankfurt 2) Object StorageOperational
  • ES-MAD (Madrid) Object StorageOperational
  • EU-Central (Frankfurt) Object StorageOperational
  • FR-PAR (Paris) Object StorageOperational
  • GB-LON (London 2)Operational
  • GB-LON (London 2) Object StorageOperational
  • ID-CGK (Jakarta) Object StorageOperational
  • IN-BOM-2 (Mumbai 2) Object StorageOperational
  • IN-MAA (Chennai) Object StorageOperational
  • IT-MIL (Milan) Object StorageOperational
  • JP-OSA (Osaka) Object StorageOperational
  • JP-TYO-3 (Tokyo 3) Object StorageOperational
  • NL-AMS (Amsterdam) Object StorageOperational
  • SE-STO (Stockholm) Object StorageOperational
  • SG-SIN-2 (Singapore 2) Object StorageOperational

+7 more components · view all on Akamai’s status page

ObservabilityOperational3 of 3 operational
  • Akamai Cloud Pulse (ACLP) - AlertsOperational
  • Akamai Cloud Pulse (ACLP) - LogsOperational
  • Akamai Cloud Pulse (ACLP) - MetricsOperational
RegionsOperational41 of 41 operational
  • AP-Northeast-2 (Tokyo 2)Operational
  • AP-South (Singapore)Operational
  • AP-Southeast (Sydney)Operational
  • AP-West (Mumbai)Operational
  • BR-GRU (São Paulo)Operational
  • CA-Central (Toronto)Operational
  • CL-SCL (Santiago)Operational
  • CO-BOG (Bogota)Operational
  • DE-FRA-2 (Frankfurt 2)Operational
  • DE-HAM (Hamburg)Operational
  • ES-MAD (Madrid)Operational
  • EU-Central (Frankfurt)Operational
  • EU-West (London)Operational
  • FR-MRS (Marseille)Operational
  • FR-PAR (Paris)Operational
  • FR-PAR-2 (Paris 2)Operational
  • ID-CGK (Jakarta)Operational
  • IN-BOM-2 (Mumbai 2)Operational
  • IN-MAA (Chennai)Operational
  • IT-MIL (Milan)Operational
  • JP-OSA (Osaka)Operational
  • JP-TYO-3 (Tokyo 3)Operational
  • MX-QRO (Queretaro)Operational
  • MY-KUL (Kuala Lumpur)Operational
  • NL-AMS (Amsterdam)Operational
  • NZ-AKL (Auckland)Operational

+15 more components · view all on Akamai’s status page

Other componentsOperational5 of 5 operational
  • Cloud Manager and APIOperational
  • Hosted DNS ServiceOperational
  • Linode.comOperational
  • LongviewOperational
  • Managed DatabasesOperational

Vendor-reported data via status.linode.com (fetched 2m ago)

OperationalDegraded PerformancePartial OutageMajor OutageMaintenanceNo dataGrade: A ≥99.9% · B ≥99% · C ≥95% · D ≥90% · F <90%

Past incidents

No incidents reported.

No incidents reported.

No incidents reported.

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedCloud Manager and API: Degraded performance · resolved after 1h 40m

No incidents reported.

  • GUARDIAN-MEASUREDGuardian-measured✓ RESOLVEDResolvedLinode API: HTTP 502 · resolved after 5m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedManaged Databases: Under maintenance · resolved after 3h
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-MIA (Miami): Under maintenance · resolved after 4h

No incidents reported.

No incidents reported.

No incidents reported.

No incidents reported.

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-Southeast (Atlanta) Object Storage: Degraded performance · resolved after 4h 5m

No incidents reported.

No incidents reported.

No incidents reported.

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedCloud Manager and API: Degraded performance · resolved after 1h 10m

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedCloud Manager and API: Degraded performance · resolved after 1d 10h

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-ORD (Chicago): Under maintenance · resolved after 10h

  • GUARDIAN-MEASUREDGuardian-measured✓ RESOLVEDResolvedLinode API: HTTP 502 · resolved after 9m
  • GUARDIAN-MEASUREDGuardian-measured✓ RESOLVEDResolvedLinode API: HTTP 502 · resolved after 5m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedCloud Manager and API: Degraded performance · resolved after 2h 45m

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedZA-JNB (Johannesburg): Under maintenance · resolved after 1h 43m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-West (Fremont): Under maintenance · resolved after 1h 43m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-Southeast (Atlanta): Under maintenance · resolved after 1h 43m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-SEA (Seattle): Under maintenance · resolved after 1h 43m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-LAX (Los Angeles): Under maintenance · resolved after 1h 43m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-IAD-2 (Washington 2): Under maintenance · resolved after 1h 43m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-IAD (Washington): Under maintenance · resolved after 1h 43m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-HOU (Houston): Under maintenance · resolved after 1h 43m

+34 more events this day not shown

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedIT-MIL (Milan): Degraded performance · resolved after 41m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedCloud Manager and API: Under maintenance · resolved after 2h 5m

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-IAD (Washington) Linode Kubernetes Engine: Degraded performance · resolved after 2h 9m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-IAD (Washington) Linode Kubernetes Engine: Degraded performance · resolved (start not recorded)
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedUS-IAD (Washington) Linode Kubernetes Engine: Degraded performance · resolved after 16m

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedCA-Central (Toronto) Block Storage: Under maintenance · resolved after 5h 40m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedCA-Central (Toronto): Under maintenance · resolved after 5h 40m

Showing the 60 most recent of the last 90 days’ events.

Vendor-reported incidents are shown from , when Guardian began recording this status feed’s transitions. Earlier vendor incidents are not shown.