outages.live
Live
ScalewayIncident ·

[VPC] - [FR-PAR-1] Metadata API through VPC is experiencing slow response time

Partial outageOfficial update
0

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.

State

Monitoring

Started

Ongoing for

1 h 11 min

Worst impact

Partial outage

Timeline

3 updates
11:0811:2611:4412:0112:19
Partial outageUpdate postedTimes in UTC

Investigating

13 min 18%

Monitoring

58 min 82%

Updates

Times in UTC

As posted by Scaleway

Monitoring

The situation should now be back to normal.

Investigating

We are continuing to investigate this issue.

Investigating

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

4
fr-par-1VPCElements - AZ - fr-par-1Elements - Products - VPC

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

57

Days with an incident

29

Median duration

15 h 5 min

This incident

92% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

18 days
median 15 h 5 min
90 days agoToday

Other Scaleway incidents

All incidents

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. Load Balancer auto-healing also stopped in that region. Scaleway is investigating the incident.

Degraded

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.

Resolved

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 the billing APIs. The incident is resolved. The situation returned to normal around 7:30 Paris time on 3 November 2026.

Resolved

Scaleway·[NETWORK] - [DC5] RPN switch is down on DC5/S9/C52

Scaleway reports that the RPN switch on DC5/S9/C52 is down, which affects the RPN service and DC5 rack S9/C52. Scaleway fixed the switch with a cold reboot. The incident is resolved and lasted about two hours and thirty-five minutes.

Resolved

Scaleway·[Generative APIs] Model mistral-small-3.2-24b-instruct-2506 unavailable.

01/11/2026 - 21:00 UTC+1 - Service started to be degradated 02/11/2026 - 2:00 UTC+1 - Service was unavailable 02/11/2026 - 9:00 UTC+1 - A fix has been implemented, service is available

Resolved

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=scaleway
Slack
/feed subscribe https://outages.live/feed.xml?providers=scaleway

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane