[Serverless Functions/Containers] - [nl-ams] - Connectivity issues
Scaleway Serverless Containers and Serverless Functions in nl-ams-1, nl-ams-2, and nl-ams-3 have connectivity issues. The create and update operations are also impacted. Scaleway monitors the situation and reports that VPC connectivity is stable now. Only Serverless Containers are impacted.
State
Monitoring
Started
Ongoing for
1 h 35 min
Worst impact
Degraded
Timeline
4 updatesIdentified
1 h 2 min 65%
Monitoring
34 min 35%
Updates
Times in UTCAs posted by Scaleway
VPC connectivity issues are now stabilized. Unlike stated previously, only Serverless Containers product is impacted. We are now monitoring the situation. Thanks for your understanding.
As of 12:00 UTC, containers shouldn't be stuck anymore in "creating" or "updating" status for an abnormal duration. Some containers with VPC support might have lost connectivity to resources inside the Private Network. A redeployment of the container triggered by users could help solving the situation, but we are investigating. Sorry again for any inconvenience.
Connectivity has been back to normal since 11:06 UTC. We are continuing to monitor the situation. We are still working on restoring create and update operations, which remain impacted.
Serverless Container, Serverless Functions are impacted.
Affected components
10Scaleway in the last 90 days
Full historyIncidents in 90 days
60
Days with an incident
31
Median duration
13 h 24 min
This incident
88% shorter than the median
Other Scaleway incidents
All incidentsScaleway·[TEM] - Delivering Issue
Scaleway Transactional Email has a delivery issue. Some customers cannot send emails or their emails stay in processing. Scaleway identified the problem and is working on a fix.
Scaleway·CKPT (pl-waw) Traces ingestion is degraded
Cockpit traces ingestion is degraded on pl-waw. The Cockpit product is affected. Scaleway reports that this incident is resolved. The outage lasted about 158 minutes.
Scaleway·[VPC] - [FR-PAR-1] Metadata API through VPC is experiencing slow response time
The Metadata API through VPC is slow in fr-par-1. DNS over TCP through VPC can also be slow. Scaleway reports that the situation should now be back to normal and is monitoring it.
Scaleway·[LOAD BALANCER] - [PAR1] - Monitoring PN down leading to autohealing mechanism stopped
Scaleway reports that Load Balancer creation and configuration do not work in the PAR1 region. Auto-healing also stopped for all load balancers in PAR1. Scaleway reports that the situation should be back to normal and continues to monitor it.
Scaleway·[DC3] [NETWORK] Switch down in DC3 Room 46 Rack B09-B10
Scaleway reports that both switches in rack DC3/S46/B09-10 went offline. Dedibox, DC3, and RPN services had degraded performance. Scaleway resolved the incident. It lasted 2 hours and 23 minutes.
Follow Scaleway
Your coding agent knows when Scaleway is down, and tells you when a failure is theirs, not yours. You can also get Scaleway incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "scaleway" and tell me if Scaleway has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=scaleway/feed subscribe https://outages.live/feed.xml?providers=scalewayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane