[BLOCKSTORAGE] - [fr-par-2] - R/W Latency spike on a fr-par-2 block storage cluster for sbs-5k and sbs-15k volumes
Scaleway reports a read/write latency spike on a fr-par-2 block storage cluster that affects sbs-5k and sbs-15k volumes in fr-par-2. Scaleway reports that the situation is back to normal. Scaleway is investigating.
State
Investigating
Started
Ongoing for
23 min
Worst impact
Degraded
Timeline
1 updateInvestigating
23 min 100%
Updates
Times in UTCAs posted by Scaleway
Today from 10h05 CEST to 10h20 CEST, a network event triggered a HA failover. But despite this mecanism, latencies were still impacted Situation is back to normal. Our teams will investigate why the failover had such impact.
Affected components
4Scaleway in the last 90 days
Full historyIncidents in 90 days
88
Days with an incident
48
Median duration
16 h 59 min
This incident
98% shorter than the median
Other Scaleway incidents
All incidentsScaleway·[Transactional Email] - [world] - Onboarding IP pool rate limited by Orange
Scaleway Transactional Email had a degraded onboarding IP pool in all regions. Orange and Wanadoo rate limited this pool and caused email congestion. Scaleway reports that the incident is resolved and that traffic to Orange returned to its normal pace. The incident lasted about 8 hours and 15 minutes.
Scaleway·[DC5] Public switch issue in DC5; room 1 ; Rack C20
A public network switch problem in DC5, room 1, rack C20 affected Dedibox connectivity. Scaleway reports that the switch recovered at 11:24 UTC and that the incident is resolved. The outage lasted about 4 hours and 49 minutes.
Scaleway·[Network] [nl-ams] Backbone connectivity issue from Amazon to Scaleway nl-ams
Scaleway reports degraded backbone connectivity from Amazon to the nl-ams region. This affects the nl-ams-1, nl-ams-2 and nl-ams-3 availability zones and the Network product. Scaleway is investigating the issue with Amazon.
Scaleway·[Block Storage] - [fr-par-1] - Write latencies increased overnight
Block Storage write latencies increased in fr-par-1. Scaleway identified the problem and reported that latencies returned to normal. The incident is resolved and lasted 70 minutes.
Scaleway·[MANAGED DATABASE] - Public and private endpoint are not correctly displayed in the console
Scaleway reports a display problem in the console for Managed Database public and private endpoints. The public endpoints can appear as unavailable. The incident is resolved and lasted about 21 hours and 29 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