Linode Status

Current Status

Connectivity Issue - All Regions

Incident Report for Linode

Postmortem

Akamai deployed a configuration change to a router in our Oslo data center (DC) at around 10:30 UTC on August 27, 2025. Following this change, Compute and CDN services across multiple geographic regions started experiencing availability issues since the change resulted in certain congesting points in the Akamai network. In parallel, Akamai's proactive monitoring detected losses extending beyond the expected site (Oslo DC). We rolled back the configuration change for immediate mitigation. The rollback action was completed at 10:38 UTC on August 27, 2025. All associated internal alerts were cleared by 10:50 UTC on August 27, 2025.

The configuration change was intended to improve monitoring for Akamai internal systems in Oslo by adjusting the communities tagged on certain prefixes, allowing them to be forwarded to the monitoring system. However, given that this change was non-critical it has been placed on hold. Normal operations can continue without it, and no functional impact was expected from the rollback.

As previously mentioned, CDN and Cloud services experienced disruptions due to this change. Affected regions included STO, MAA, BOM, SG2, FRA2, AMS, as well as select routes within major European cloud environments. CDN disruptions were most prominent in Australia, though intermittent impact was observed globally, as confirmed by internal monitoring.

At this time, recurrence of the issue is unlikely. A detailed review of the change and its deployment process is underway, including targeted lab testing to determine the root cause. The configuration change will remain paused until a full assessment is completed.

Akamai will continue to investigate the root cause and will take appropriate preventive actions. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to our systems in an effort to prevent recurrence.

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Posted Aug 28, 2025 - 15:47 UTC

Resolved

We haven’t observed any additional connectivity issues across all regions, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Posted Aug 27, 2025 - 17:49 UTC

Monitoring

Between 10:35 UTC and 10:50 UTC on August 27, 2025, some users may have experienced elevated latency or connectivity issues across all regions. Our preliminary investigation indicates the issue was linked to a router configuration change. The change was promptly rolled back at 10:39 UTC after anomalies were detected.

We believe the rollback has mitigated the immediate impact. Our teams are actively investigating the root cause of the issue and assessing the full scope of its effects. We will share further updates as soon as more information becomes available.

We apologize for the disruption and appreciate your patience as we continue to resolve this matter.

If you are still experiencing issues, please open a Support ticket for assistance.
Posted Aug 27, 2025 - 13:10 UTC
This incident affected: Regions (US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta), 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)).