[DC3] [NETWORK] Switch down in DC3 Room 46 Rack B09-B10
Scaleway reports network problems in DC3 Room 46 Rack B09-B10. The issue affects the Dedibox and RPN components in DC3. Scaleway is investigating. Two switches in the rack went offline.
State
Investigating
Started
2 h ago
2026-11-03 08:35 UTC
Ongoing for
1 h 34 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 34 min 100%
Updates
Times in UTCAs posted by Scaleway
Both switches in the rack DC3/S46/B09-10 went offline.
Both switches in the rack DC3/S46/B10 went offline.
Affected components
6Scaleway in the last 90 days
Full historyIncidents in 90 days
56
Days with an incident
29
Median duration
16 h 45 min
This incident
91% shorter than the median
Other Scaleway incidents
All incidentsScaleway·[LBAS] - [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.
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.
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.
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
Scaleway·[Container Registry] FR-PAR API unreacheable upstream request timeout.
Between 8:00 PM and 9:30 PM, requests to the Container Registry API in the FR-PAR region returned the following error: “Upstream request timeout.”
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