[Block Storage] - fr-par-1 - Write latency increase due to background operations
Scaleway Block Storage in fr-par-1 has higher write latency. The affected components are Block Storage and Elements in the AZ fr-par-1. Scaleway identified the cause as background operations and is working to process the remaining tasks faster. Write latency should return to normal in a few hours.
State
Identified
Started
Ongoing for
31 min
Worst impact
Degraded
Timeline
1 updateIdentified
31 min 100%
Updates
Times in UTCAs posted by Scaleway
Since 22h UTC, mean write latencies slowly increased on one Block cluster on fr-par-1 due to background operations pilling up overnight until 05h19 UTC. Latencies are not increasing anymore and the cluster is processing the remaining operations. The Block Storage team is working to speed up the processing of the remaining tasks. Write latencies are expected to return to normal in a few hours
Affected components
4Scaleway in the last 90 days
Full historyIncidents in 90 days
63
Days with an incident
33
Median duration
16 h 45 min
This incident
97% shorter than the median
Other Scaleway incidents
All incidentsScaleway·[DEDIBOX] - RPNv1 network unavailability in DC3 room 4-4 corridors C and D
Scaleway reports RPNv1 network unavailability in DC3, room 4-4, corridors C and D. This affects multiple racks. The first router of the pair is back online. A fix is in place and Scaleway monitors the results.
Scaleway·[DC3] Switch issues in room 4-4 rack B14 / B15
Scaleway reports that a switch is unavailable in room 4-4, rack B14 and B15, in the DC3 datacenter. This affects Dedibox services in DC3. Scaleway replaced the switch in B14 and put a fix in place. Scaleway monitors the result now.
Scaleway·[Transactionnal Email] - Delivering Issue
Scaleway Transactional Email had a delivering issue. Some emails got stuck while processing or sending. Scaleway reports that the incident is resolved and that it lasted about 3 hours and 6 minutes.
Scaleway·[Serverless Functions/Containers] - [nl-ams] - Connectivity issues
Scaleway Serverless Containers in the nl-ams region did not work correctly. Some users got HTTP 5xx errors, some containers stayed in creating or updating status, and some containers with VPC support lost connectivity to Private Network resources. Scaleway reports that the incident is resolved. It lasted about 4 hours and 29 minutes.
Scaleway·CKPT (pl-waw) Traces ingestion is degraded
Cockpit traces ingestion is degraded on pl-waw. The Cockpit product is affected. Scaleway reports that this incident is resolved. The outage lasted about 158 minutes.
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.live/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.live/feed.xml?providers=scaleway/feed subscribe https://outages.live/feed.xml?providers=scalewayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane