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

- Provider: [Scaleway](https://down.guide/scaleway)
- Level: confirmed
- Impact: Degraded
- lasted 20h 45m
- started 2026-08-17 16:41 UTC
- fr-par-1, fr-par-2, fr-par-3 +1
- id: DWN-e70ed425a4
- Official page: https://stspg.io/bgkykn7lx729

## Updates from Scaleway
### 2026-08-17 16:41 UTC: 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.

### 2026-08-17 16:48 UTC: monitoring
We have finished rolling back the faulty deployment. Situation should be good now for all users.

### 2026-08-18 13:26 UTC: 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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).