[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.
State
Identified
Started
Ongoing for
21 min
Worst impact
Degraded
Timeline
2 updatesIdentified
21 min 100%
Updates
Times in UTCAs posted by Scaleway
The affected network switch will be replaced tomorrow, Friday, November 13, 2026, starting at 10:00 a.m. CET, following several recent incidents We will provide further updates once the replacement is completed.
The affected network switch will be replaced tomorrow, Friday, November 13, 2026, starting at 10:00 a.m. CET, following several recent incidents We will provide further updates once the replacement is completed.
Affected components
4Scaleway in the last 90 days
Full historyIncidents in 90 days
75
Days with an incident
38
Median duration
10 h 33 min
This incident
97% shorter than the median
Other Scaleway incidents
All incidentsScaleway·[Network] [DC3]- Room S45 rack D14 - Public switch reboot
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.
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.
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
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.
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.
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.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.
https://outages.live/feed.xml?providers=scaleway/feed subscribe https://outages.live/feed.xml?providers=scalewayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane