outages.live
Live
ScalewayIncident ·

[Network] [DC3]- Room S45 rack D14 - Public switch reboot

ResolvedOfficial update
0

At 2026-11-12 16:53:02 CET, the public switch in DC3 room S45 rack D14 rebooted. All servers attached to it have lost public connectivity for approximately 10 mins.

The latest update from Scaleway.

State

Resolved

Started

Lasted

1 min

Worst impact

Degraded

Timeline

1 update
16:2116:2216:2216:2216:22
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by Scaleway

Resolved

At 2026-11-12 16:53:02 CET, the public switch in DC3 room S45 rack D14 rebooted. All servers attached to it have lost public connectivity for approximately 10 mins.

Affected components

4
DediboxDC3Dedibox - Datacenters - DC3Dedibox - Products - Dedibox

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

75

Days with an incident

38

Median duration

10 h 33 min

This incident

100% shorter than the median

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

22 days
median 10 h 33 min
90 days agoToday

Other Scaleway incidents

All incidents

Scaleway·[Network] [DC3]- Room S45 rack D14 - Public switch reboot

Scaleway reports a public switch problem in room S45, rack D14 at DC3. This affects Dedibox services in that datacenter. Scaleway identified the problem. Scaleway will replace the affected network switch on Friday, November 13, 2026, starting at 10:00 a.m. CET.

Degraded

Scaleway·[Containers/Functions] - [fr-par] - private endpoints might not be available

Scaleway reports that private endpoints for Serverless Containers and Serverless Functions in the fr-par region may not be available. Only some containers attached to a private network are affected. Scaleway is investigating.

Degraded

Scaleway·[Generative-Apis] [fr-par] - mistral-small-3.2-24b-instruct-2506 outage

[11/12 - 9:45 UTC+1] The incident has been mitigated, service is back to normal

Resolved

Scaleway·[ElasticMetal] - [world] - The private_network option is not working as expected in the Terraform provider.

The privatenetwork option does not work as expected in the Scaleway Terraform provider for Elastic Metal in all regions. Scaleway reports that it is investigating the problem.

Degraded

Scaleway·[WEBHOSTING] [fr-par] pf-1010.whm.fr-par.scw.cloud

Scaleway reports that the webhosting service pf-1010.whm.fr-par.scw.cloud in the fr-par region did not work. Scaleway identified a failed MySQL upgrade and performed a rollback with a backup. The incident is resolved and lasted about 47 minutes.

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