[Serverless Functions/Containers] - [nl-ams] - Connectivity issues
Scaleway reports connectivity issues for Serverless Functions and Serverless Containers in the nl-ams region. The affected components include nl-ams-1, nl-ams-2, and nl-ams-3. Scaleway identified the issue and states that connectivity is back to normal since 11:06 UTC, but create and update operations stay impacted.
State
Identified
Started
Ongoing for
43 min
Worst impact
Degraded
Timeline
2 updatesIdentified
43 min 100%
Updates
Times in UTCAs posted by Scaleway
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
10 h 33 min
This incident
93% shorter than the median
Other Scaleway incidents
All incidentsScaleway·CKPT (pl-waw) Traces ingestion is degraded
Scaleway Cockpit traces ingestion is degraded on the pl-waw region. This incident is resolved. It lasted 2 hours and 38 minutes.
Scaleway·[VPC] - [FR-PAR-1] Metadata API through VPC is experiencing slow response time
Scaleway reports slow response time on the Metadata API through VPC in the fr-par-1 region. DNS over TCP through VPC may also be slow. Scaleway reports that the situation should now be back to normal and is monitoring it.
Scaleway·[SERVERLESS] - [fr-par] - Some Serverless Containers are unreachable
Some Serverless Containers in the fr-par region were unreachable. The affected components were fr-par-1, fr-par-2, fr-par-3, and Serverless Container. Scaleway reports that the incident is resolved and that it lasted about 4 hours and 10 minutes.
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 fr-par-1 region. The provider also reports that Load Balancer auto-healing stopped in fr-par-1. Scaleway states 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 switches in DC3 Room 46 Rack B09-B10 went offline. This affected Dedibox, DC3, and RPN. Scaleway states that the incident is resolved. 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.cc/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.cc/feed.xml?providers=scaleway/feed subscribe https://outages.cc/feed.xml?providers=scalewayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane