Outage in Scaleway
[Serverless Containers] - [fr-par] - issues connecting to resources inside Private Network
Resolved MinorIncident Report
Summary AI Generated
Between 09:20 and 16:15 UTC on August 17, 2026, Scaleway Serverless Containers in the fr-par region lost connectivity to resources within their Private Networks, causing timeouts and connection errors. The issue affected Private Networks with ACLs enabled and VPCs with routing disabled, due to blackholed traffic triggered by a faulty deployment. Scaleway resolved the incident by rolling back the problematic component at 16:15 UTC.
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.
Trusted by 1,000+ teams
The Status Page Aggregator with Early Outage Detection
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
RESOLVED
9 days ago - at 08/18/2026 01:26PM
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.
MONITORING
10 days ago - at 08/17/2026 04:48PM
We have finished rolling back the faulty deployment. Situation should be good now for all users.
INVESTIGATING
10 days ago - at 08/17/2026 04:41PM
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.
Latest Scaleway outages
[SEDB] - [fr-par] - Endpoint not displayed correctly in the console - about 15 hours ago
[DNSE] - [waw1] - no update on DNS - about 24 hours ago
[BMNA] - global - epp instability for some TLDs - 2 days ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
