Live / Scaleway / Incident
Scaleway: [LOAD BALANCER] - [PAR1] - Monitoring PN down leading to autohealing mechanism stopped
Scaleway · scaleway.comMinor incidentResolved2026-11-10 13:53 UTC
Public — what happened
Summary
Scaleway reported a minor incident affecting its Load Balancer service in the PAR1 location, starting 3 November 2026 at 09:54 UTC. The company said customers could have trouble creating or configuring load balancers, and that the automatic recovery feature was not working, which it attributed to a failure in an internal metadata system. On 4 November at 08:21 UTC Scaleway said things should be back to normal and it was monitoring, and it marked the incident resolved on 10 November at 13:53 UTC.
Affected
fr-par-1, Load Balancer
Timeline
- Started — 2026-11-03 09:54 UTC
- Investigating — 2026-11-03 09:54 UTC (3 updates)
- Monitoring — 2026-11-04 08:21 UTC
- Resolved — 2026-11-10 13:53 UTC · 7 days after it started
What SquidGrid measured
SquidGrid measured 292 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 46, 2026, our weekly internet health report.