Linode incident: Service Issue - Paris (FR-PAR3)

Affected components

• FR-PAR (Paris)

1. postmortemJun 5, 2026, 11:01 UTC

   On May 22, 2026 between approximately 09:10 and 11:30 UTC, connectivity issues were experienced in Paris \(FR-PAR3\) datacenter. During the impact window, customers may have experienced intermittent connection timeouts and errors for services deployed in the Paris datacenter. Our investigation established that connectivity to the host was affected as both of our transits in FRA3 flapped at the exact same time and that triggered high route churn which in result caused packet loss. On analyzing further on why both of our transits flapped at the exact same time, we engaged our Data Center provider and it was identified that during a planned maintenance in the data center, both operator rooms, which support network connectivity, lost power for several minutes, resulting in a complete isolation of the availability zone. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and preven

2. resolvedMay 26, 2026, 06:15 UTC

   We haven’t observed any additional connectivity issues in our Paris data center, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

3. monitoringMay 22, 2026, 13:14 UTC

   The issue subsided by 11:30 UTC on May 22, 2026, the impact was observed between 09:10 UTC to 11:30 UTC on May 22, 2026. We are actively monitoring to ensure that the service remains stable . If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

4. investigatingMay 22, 2026, 12:24 UTC

   We are continuing to investigate the issue

5. investigatingMay 22, 2026, 11:22 UTC

   We are investigating a service issue affecting traffic in our Paris data center. We will share additional updates as we have more information.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Linode's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Mailgun: Delayed sending in EUCritical · May 25, 2026, 12:18 UTC
• Render: Upstream provider outage causing delays provisioning custom domainsMajor · May 22, 2026, 15:53 UTC
• Elasticsearch: Missing Metrics in Cloud Console - Azure North EuropeMajor · May 23, 2026, 21:42 UTC
• Pinecone: [Serverless][AWS][us-west-2] 5xx errors and longer response times on upsert requests for some indexes.Major · May 25, 2026, 13:41 UTC
• Netlify: Support Communication Delivery IssuesMajor · May 25, 2026, 15:31 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
• Snyk: Snyk Tests for Gradle projects DegradationMinor · May 22, 2026, 02:29 UTC
• Clerk: Issue with Provisioning DomainsMinor · May 22, 2026, 15:48 UTC
• ClickHouse Cloud: Capacity issues in AWS us-east-1 region affecting provisioning timesMinor · May 22, 2026, 16:11 UTC
• Expo: Some project overview and hosting pages not loading on expo.devMinor · May 22, 2026, 16:17 UTC

How often does Linode have incidents?

Linode reported 10 incidents in the last 90 days. A typical incident lasted 2h 15m. See Linode's uptime and incident history