[DC3] Switch issues in room 4-4 rack B14 / B15
Scaleway reports switch issues in room 4-4, rack B14 and B15, at its DC3 datacenter. These issues degrade Dedibox services in DC3. Scaleway replaced the switch in B14, put a fix in place, and now monitors the results.
State
Monitoring
Started
Ongoing for
4 h 26 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
2 h 45%
Identified
1 h 18 min 29%
Monitoring
1 h 7 min 25%
Updates
Times in UTCAs posted by Scaleway
A fix has been implemented and we are monitoring the results.
A technicien is actually replacing the switch in B14
Switch is currently unavailable. We are investigating.
Affected components
4Scaleway in the last 90 days
Full historyIncidents in 90 days
62
Days with an incident
32
Median duration
15 h 5 min
This incident
71% shorter than the median
Other Scaleway incidents
All incidentsScaleway·[Transactionnal Email] - Delivering Issue
Scaleway Transactional Email had a delivering issue that affected some emails in the Elements products. Scaleway identified the issue and restored outbound traffic. The incident is resolved and lasted about 3 hours and 6 minutes.
Scaleway·[Serverless Functions/Containers] - [nl-ams] - Connectivity issues
Scaleway Serverless Containers in the nl-ams region had connectivity problems. Some containers returned HTTP 5xx errors, were stuck in creating or updating, or lost Private Network connectivity. Scaleway reports the incident resolved. It lasted about 4 hours and 29 minutes.
Scaleway·CKPT (pl-waw) Traces ingestion is degraded
Scaleway Cockpit traces ingestion is degraded on the pl-waw region. This incident is resolved. It lasted 2 hours and 38 minutes.
Scaleway·[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.
Scaleway·[SERVERLESS] - [fr-par] - Some Serverless Containers are unreachable
Some Serverless Containers in the fr-par region were unreachable. The affected components were fr-par-1, fr-par-2, fr-par-3, and Serverless Container. Scaleway reports that the incident is resolved and that it lasted about 4 hours and 10 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