Provider
ScalewayIncident detail
[Serverless Containers] - [fr-par] - issues connecting to resources inside Private Network
Resolved incidentMinor
Timeline window
to
Outage alerts
Get alerted the next time Scaleway breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Scaleway posted, oldest to newest, exactly as it appeared on their official status page.
Investigating
On a small subset of our fr-par infrastructure, between 2026-08-17 09:20 UTC and 2026-08-17 16:15 UTC, some containers attached to a Private Network were not able to reach resources inside that PN. This issue is likely due to a faulty deployment, that we have reverted at 2026-08-17 16:15 UTC.
Containers should now be able to reach resources in their Private Network as before.
If your container has faced issues like "timeouts" or "connection error" while trying to reach a resource through their private endpoint during the time range above, the issues are likely linked. If you still continue to face these errors, feel free to open a support ticket.
We sincerely apologize for any inconvenience.
Monitoring
We have finished rolling back the faulty deployment. Situation should be good now for all users.
Resolved
After investigation, we have found the root cause.
The issue happened because of blackholed traffic, but only on some Private Networks with a specific configuration:
- PNs with ACLs
- PNs inside VPCs with "enable_routing" set to false
Anyway, we have rolled back the component causing the issues, so this error shouldn't happen anymore.
Sorry again for any inconvenience.
Keep exploring
More from Scaleway
Neighboring incidents on Scaleway's timeline and the rest of their record on OutageDeck.