Scaleway incident

[Serverless Containers] - [fr-par] - issues connecting to resources inside Private Network

Resolved after 20 hours 44 minutes, affecting fr-par-1 and fr-par-2 and 1 more, on August 17, 2026.

resolved Aug 18, 2026, 01:26 PM UTC

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.

Started
Aug 17, 2026, 04:41 PM UTC
Resolved
Aug 18, 2026, 01:26 PM UTC
Duration
20h 44m
Detected by Pingoru
Aug 17, 2026, 04:41 PM UTC

Affected components

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

Update timeline

  1. investigating Aug 17, 2026, 04:41 PM 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.

  2. monitoring Aug 17, 2026, 04:48 PM UTC

    We have finished rolling back the faulty deployment. Situation should be good now for all users.

  3. resolved Aug 18, 2026, 01:26 PM UTC

    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.

Your product runs on more than Scaleway

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →