Live / Scaleway / Incident
Scaleway: Cockpit (pl-waw) Traces ingestion is degraded
Scaleway · scaleway.comMinor incidentResolved2026-11-04 15:15 UTC
Public — what happened
Summary
Scaleway reported a minor problem with its Cockpit monitoring service in the pl-waw region (Warsaw), where trace ingestion was degraded. The company said that starting at 12:37 UTC on 2026-11-04, some customers might see errors when sending traces. Scaleway did not give a cause in its updates, and it marked the incident resolved at 15:15 UTC the same day.
Affected
Cockpit
Timeline
- Started — 2026-11-04 12:37 UTC
- Investigating — 2026-11-04 12:37 UTC
- Resolved — 2026-11-04 15:15 UTC · 2h 38m after it started
What SquidGrid measured
SquidGrid measured 228 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.