Skip to main content
Akamai Cloud (Linode)

Emerging Service Issue - Managed Databases - All Regions

Degraded Lasted 21h 27m · started · Akamai Cloud (Linode)'s page

Level
confirmed
Worst impact
Degraded
Components
US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta), Managed Databases, US-IAD (Washington), US-ORD (Chicago), CA-Central (Toronto), EU-West (London), EU-Central (Frankfurt), FR-PAR (Paris), AP-South (Singapore), AP-Northeast-2 (Tokyo 2), AP-West (Mumbai), AP-Southeast (Sydney), SE-STO (Stockholm), US-SEA (Seattle), IT-MIL (Milan), JP-OSA (Osaka), IN-MAA (Chennai), ID-CGK (Jakarta), BR-GRU (São Paulo), NL-AMS (Amsterdam), US-MIA (Miami), US-LAX (Los Angeles), ES-MAD (Madrid), AU-MEL (Melbourne), GB-LON (London 2), IN-BOM-2 (Mumbai 2), SG-SIN-2 (Singapore 2), DE-FRA-2 (Frankfurt 2), JP-TYO-3 (Tokyo 3), ZA-JNB (Johannesburg), NZ-AKL (Auckland), CO-BOG (Bogota), US-DEN (Denver), DE-HAM (Hamburg), US-HOU (Houston), MY-KUL (Kuala Lumpur), FR-MRS (Marseille), MX-QRO (Queretaro), CL-SCL (Santiago), FR-PAR-2 (Paris 2), US-IAD-2 (Washington 2)
Regions
ap-northeast-2, apac, au, ca, eu, latam, us
Down Index
52of 100

What to do

  • Check whether you use Akamai Cloud (Linode) US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta) and 40 more in ap-northeast-2, apac, au, ca. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 21h 27m it lasted.

    Anything that failed between 2026-07-06 18:04 UTC and 2026-07-07 15:31 UTC may need a replay.
  • Subscribe to Akamai Cloud (Linode)'s feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=linode works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Akamai Cloud (Linode) 2

  1. investigating

    Our team is investigating an emerging service issue affecting Managed Databases across all regions. Customers may experience latency when provisioning new databases or deleting existing ones. There is no observed impact to the performance or availability of active, running databases at this time. We will provide updates as more information becomes available.

    provider

  2. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-5e89aa8808

Is Akamai Cloud (Linode) still down?

No, this incident was resolved 2026-07-07 15:31 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.

How long did it last?

21h 27m, from 2026-07-06 18:04 UTC to 2026-07-07 15:31 UTC, by the times Akamai Cloud (Linode) posted.

What was affected?

Akamai Cloud (Linode) named US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta) and 40 more in ap-northeast-2, apac, au, ca.

What caused it?

Akamai Cloud (Linode) hasn't published a root cause. If it does, it shows here.

Where does this come from?

Akamai Cloud (Linode)'s official status page, https://status.linode.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.