Live / Scaleway / Incident
Scaleway: [Serverless Functions/Containers] - [nl-ams] - Connectivity issues
Scaleway · scaleway.comMinor incidentResolved2026-11-05 15:52 UTC
Public — what happened
Summary
Scaleway said a planned maintenance in its Amsterdam (nl-ams) region did not go as intended and caused problems for its Serverless Containers product, with an early note that Serverless Functions were affected too, which it later corrected. The company said users saw error responses when calling their containers, some containers got stuck while being created or updated, and some containers using private networking lost connection to their resources. Scaleway said connectivity returned to normal around 11:06 UTC, the stuck containers and private network problems were cleared by about 12:00 and 12:20 UTC, and it marked the incident resolved at 15:52 UTC. It attributed the trouble to a faulty step in the maintenance, said the upgrade was only partly applied and the rest postponed, and said it would run more tests first.
Affected
nl-ams-1, nl-ams-2, nl-ams-3, Serverless Container, Serverless Functions
Timeline
- Started — 2026-11-05 11:22 UTC
- Identified — 2026-11-05 11:22 UTC (4 updates)
- Monitoring — 2026-11-05 12:21 UTC
- Resolved — 2026-11-05 15:52 UTC · 4h 29m after it started
What SquidGrid measured
SquidGrid measured 256 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.