Live  /  Scaleway  /  Incident

Scaleway: [Containers/Functions] - [fr-par] - private endpoints might not be available

Scaleway · scaleway.comMinor incidentResolved2026-11-12 17:36 UTC
Public — what happened

Summary

Scaleway said a small share of its Containers and Functions in the fr-par region that were attached to private networks had problems. Some customers could not reach their containers through private endpoints, and some workloads had errors when connecting to resources inside a private network. The company reported the trouble began around 14:00 UTC on 2026-11-12 and posted its first notice at 14:29 UTC. It marked the incident resolved at 17:36 UTC, saying the impact lasted roughly until 15:30 UTC, and it did not name a cause.

Affected

fr-par-1, fr-par-2, fr-par-3, Serverless Container, Serverless Functions

As listed on Scaleway’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

What SquidGrid measured

SquidGrid measured 233 internet paths into Scaleway’s network during this incident. None of them ran meaningfully slower than the same paths the day before.

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 see
Customers 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 47, 2026, our weekly internet health report.

The full archive is on the Scaleway status & history page.

Related: Scaleway status & history. SquidGrid is not affiliated with Scaleway.