Live / Scaleway / Incident
Scaleway: [fr-par-1] Latencies spikes during the day following capacity increase in one of block storage cluster
Scaleway · scaleway.comMinor incidentResolved2026-11-05 14:35 UTC
Public — what happened
Summary
Scaleway said that block storage in its fr-par-1 location had periodic spikes in response time, most noticeable during the day, and that its MRDB product was also affected. The company said the spikes began on 26 October after a new rack was added to one of its storage clusters, and that they were tied to writing data on some of the new disks. Scaleway reported applying a fix to one server on 29 October, then rolling it out more widely, with data moves done slowly to avoid making delays worse. It said all new servers were fixed by 4 November and marked the incident resolved on 5 November at 14:35 UTC.
Affected
Block Storage, Databases, Instances
Timeline
- Started — 2026-10-29 11:01 UTC
- Identified — 2026-10-29 11:01 UTC (4 updates)
- Monitoring — 2026-11-04 16:40 UTC
- Resolved — 2026-11-05 14:35 UTC · 7 days after it started
What SquidGrid measured
SquidGrid measured 272 internet paths into Scaleway’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Scaleway against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Scaleway: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Scaleway report →
More from Scaleway
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.