[fr-par] Partial unavailability affecting an Object Storage cluster
This incident has been resolved.
The latest update from Scaleway.
State
Resolved
Started
12 d ago
2026-10-20 15:21 UTC
Lasted
21 h 2 min
until 2026-10-21 12:23 UTC
Worst impact
Degraded
Timeline
5 updatesIdentified
27 min 2%
Monitoring
20 h 35 min 98%
Updates
Times in UTCAs posted by Scaleway
This incident has been resolved.
Object Storage services in the fr-par region have returned to normal operating conditions following the deployment of the fix. Our teams continue to closely monitor the infrastructure to ensure service stability before marking the incident as resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
Following an infrastructure deployment, connectivity was disrupted across several racks, potentially impacting Object Storage customers in the fr-par region through increased latency and request errors. The issue has been identified, and our engineering teams are currently deploying a fix to restore normal service operations.
Affected components
2Scaleway in the last 90 days
Full historyIncidents in 90 days
51
Days with an incident
27
Median duration
16 h 45 min
This incident
1.3× the median
Other Scaleway incidents
All incidentsScaleway·[Container Registry] FR-PAR API unreacheable upstream request timeout.
Between 8:00 PM and 9:30 PM, requests to the Container Registry API in the FR-PAR region returned the following error: “Upstream request timeout.”
Scaleway·[fr-par] [Serverless SQL DB] Backups will be suspended on Friday and Saturday nights
Scaleway Serverless SQL DB backups do not run in the fr-par region. The impact is degraded on Serverless-Database components. Scaleway identified the cause and suspended backups on Friday and Saturday nights. Backups start again on Monday morning.
Scaleway·[NL-AMS] - 20% of client requests failed with HTTP 503 errors
October 28, 2026 – 16:14 to 16:27 UTC Approximately 20% of Serverless Containers requests in nl-ams returned HTTP 503 errors, and some active client connections may have been interrupted.
Scaleway·[fr-par-1] Latencies spikes during the day following capacity increase in one of block storage cluster
Scaleway Block Storage has latency spikes in the fr-par-1 region. This degrades Block Storage, Databases, and Instances. Scaleway identified the problem and applies a fix rack by rack. Data must be removed first, so migrations run slowly and continue through the weekend.
Scaleway·[fr-par] [Serverless SQL DB] All SQL databases are unavailable
This incident has been resolved.
Follow Scaleway
Your coding agent knows when Scaleway is down, and tells you when a failure is theirs, not yours. You can also get Scaleway 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 "scaleway" and tell me if Scaleway 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=scaleway/feed subscribe https://outages.cc/feed.xml?providers=scalewayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane