outages.live
Live
ScalewayIncident ·

[DC3] [NETWORK] Switch down in DC3 Room 46 Rack B09-B10

DegradedOfficial update
0

Scaleway reports that two network switches are down in rack B09-B10 in Room 46 of DC3. This degrades Dedibox and RPN services in DC3. Scaleway is investigating the incident.

State

Investigating

Started

Ongoing for

1 h 59 min

Worst impact

Degraded

Timeline

2 updates
08:3509:0409:3410:0410:34
DegradedUpdate postedTimes in UTC

Investigating

1 h 59 min 100%

Updates

Times in UTC

As posted by Scaleway

Investigating

Both switches in the rack DC3/S46/B09-10 went offline.

Investigating

Both switches in the rack DC3/S46/B10 went offline.

Affected components

6
DediboxDC3RPNDedibox - Datacenters - DC3Dedibox - Products - DediboxDedibox - Products - RPN

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

57

Days with an incident

29

Median duration

16 h 45 min

This incident

88% shorter than the median

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

18 days
median 16 h 45 min
90 days agoToday

Other Scaleway incidents

All incidents

Scaleway·[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.

Degraded

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.

Degraded

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.

Resolved

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.

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane