Connectivity Issue - FR-PAR-2 (Paris 2)
Connectivity does not work in the FR-PAR-2 (Paris 2) data center. Users can have connection timeouts and errors for all services in this data center. Akamai Cloud (Linode) is investigating the issue.
State
Investigating
Started
2 h ago
2026-11-02 18:03 UTC
Ongoing for
1 h 45 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 45 min 100%
Updates
Times in UTCAs posted by Akamai Cloud (Linode)
We are continuing to investigate the issue.
Our team is investigating an issue affecting connectivity in our FR-PAR-2 data center. During this time, users may experience intermittent connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information.
Affected components
2Akamai Cloud (Linode) in the last 90 days
Full historyIncidents in 90 days
29
Days with an incident
89
Median duration
6 h 29 min
This incident
73% shorter than the median
Other Akamai Cloud (Linode) incidents
All incidentsAkamai Cloud (Linode)·Connectivity Issue - IN-MAA and IN-BOM-2
Connectivity does not work in the IN-MAA (Chennai) and IN-BOM-2 (Mumbai 2) data centers. The provider reports that the incident is resolved. The outage lasted about 3 hours and 12 minutes.
Akamai Cloud (Linode)·Service Issue - US-Southeast (Atlanta)
A service issue affects US-Southeast (Atlanta) and Regions - US-Southeast (Atlanta). Akamai Cloud reports that the issue is resolved. The issue lasted from 31 October 2026 to 2 November 2026, about 48 hours.
Akamai Cloud (Linode)·Customer Security Advisory: CVE-2026-98432
Akamai Cloud (Linode) reports a security advisory for CVE-2026-98432 on its compute platform. The provider is investigating and has deployed network rules that drop IPv4 packets with optional headers on public and VPC interfaces. Akamai advises customers to apply OS updates when available.
Akamai Cloud (Linode)·Service Issue - Block Storage (BR-GRU)
Block Storage does not work in the BR-GRU (São Paulo) region. Akamai Cloud reports that a fix is in place and the state is monitoring.
Akamai Cloud (Linode)·Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)
Akamai Cloud reports a connectivity problem between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2). The service is degraded in these two regions. Akamai Cloud moved the incident to monitoring and continues to monitor the impact.
Follow Akamai Cloud (Linode)
Your coding agent knows when Akamai Cloud (Linode) is down, and tells you when a failure is theirs, not yours. You can also get Akamai Cloud (Linode) incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "linode" and tell me if Akamai Cloud (Linode) has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=linode/feed subscribe https://outages.cc/feed.xml?providers=linodeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane