Linode incident

Emerging Service Issue - Managed Databases - All Regions

Linode experienced a notice incident on July 6, 2026 affecting US-East (Newark) and US-Central (Dallas) and 1 more component, lasting 21h 27m. The incident has been resolved; the full update timeline is below.

Started: Jul 06, 2026, 06:04 PM UTC
Resolved: Jul 07, 2026, 03:31 PM UTC
Duration: 21h 27m
Detected by Pingoru: Jul 06, 2026, 06:04 PM UTC

Affected components

US-East (Newark)US-Central (Dallas)US-West (Fremont)US-Southeast (Atlanta)Managed DatabasesUS-IAD (Washington)US-ORD (Chicago)CA-Central (Toronto)EU-West (London)EU-Central (Frankfurt)

Update timeline

investigating Jul 06, 2026, 06:04 PM UTC

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.
resolved Jul 07, 2026, 03:31 PM UTC

This incident has been resolved.