Live / Scaleway / Incident
Scaleway: [SERVERLESS] - [fr-par] - Some Serverless Containers are unreachable
Scaleway · scaleway.comMinor incidentResolved2026-11-03 14:13 UTC
Public — what happened
Summary
Scaleway said that some of its Serverless Containers in the fr-par region could not be reached, starting at 10:03 UTC on 2026-11-03. The company said the problem appeared to come from a load balancer being down, which affected only some of the containers in that region. By 10:06 UTC Scaleway said it had found the problem on the load balancer side and that it was fixed, and it kept watching without expecting a repeat. It marked the incident resolved at 14:13 UTC and rated it minor.
Affected
fr-par-1, fr-par-2, fr-par-3, Serverless Container
Timeline
- Started — 2026-11-03 10:03 UTC
- Investigating — 2026-11-03 10:03 UTC
- Monitoring — 2026-11-03 10:06 UTC
- Resolved — 2026-11-03 14:13 UTC · 4h 10m after it started
What SquidGrid measured
SquidGrid measured 265 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.