[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.
State
Monitoring
Started
Ongoing for
1 h 23 min
Worst impact
Partial outage
Timeline
5 updatesInvestigating
13 min 15%
Monitoring
1 h 11 min 85%
Updates
Times in UTCAs posted by Scaleway
The situation should now be back to normal.
We are continuing to investigate this issue.
We are currently experiencing slow response time on Metadata API through VPC. This started at 09:00 UTC. DNS over TCP through VPC may also experience slow response time.
We are continuing to investigate this issue.
We are currently experiencing slow response time on Metadata API through VPC. This started at 09:00 UTC. DNS over TCP through VPC may also experience slow response time.
Affected components
4Scaleway in the last 90 days
Full historyIncidents in 90 days
58
Days with an incident
29
Median duration
15 h 5 min
This incident
91% shorter than the median
Other Scaleway incidents
All incidentsScaleway·[SERVERLESS] - [fr-par] - Some Serverless Containers are unreachable
Scaleway reports that some Serverless Containers are unreachable in the fr-par region. This affects fr-par-1, fr-par-2, and fr-par-3. Scaleway identified the problem on the load balancer side and it is now resolved. Scaleway monitors the state and does not expect the problem to occur again.
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 (PAR1) region. Load balancers in PAR1 lost connectivity with the internal metadata API, and the auto-healing mechanism stopped. Scaleway is investigating the issue.
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.
Scaleway·[BILLING] - Billing consumptions in November are not up-to-date
Scaleway billing consumptions for November were not up to date in the billing console and billing APIs. Scaleway reports that the incident is resolved. The outage lasted about 17 hours.
Scaleway·[NETWORK] - [DC5] RPN switch is down on DC5/S9/C52
The RPN switch on DC5/S9/C52 is down. The RPN service and Dedibox in the DC5 region do not work. Scaleway reports that the incident is resolved. It lasted 2 hours and 36 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