Live / Scaleway / Incident
Scaleway: [VPC] - [FR-PAR-1] Metadata API through VPC is experiencing slow response time
Scaleway · scaleway.comMajor incidentmonitoring2026-11-03 11:20 UTC
Public — what happened
Summary
Scaleway reported a major issue in its FR-PAR-1 location in which the Metadata API reached through VPC was responding slowly. The company said this began at 09:00 UTC on 2026-11-03 and that DNS through VPC might also have been slow. It posted its first notice at 11:08 UTC and said it was still investigating a minute later. At 11:20 UTC Scaleway said things should be back to normal and moved the incident to monitoring, and it had not marked it fully resolved. No cause was given in the text.
Affected
fr-par-1, VPC
Timeline
- Started — 2026-11-03 11:08 UTC
- Investigating — 2026-11-03 11:08 UTC (2 updates)
- Monitoring — 2026-11-03 11:20 UTC
- Ongoing at last check.
What SquidGrid measured
SquidGrid measured 289 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.