[DC3] Interlink Router device at dc3 lost the connexion with the Interlink Route Reflector
Scaleway reports that the ILR device at DC3 lost the connection with the ITL RR. Customers connected to this router may have had a disruption to production traffic for approximately 4 minutes. Scaleway is investigating.
State
Investigating
Started
Ongoing for
30 min
Worst impact
Notice
Timeline
1 updateInvestigating
30 min 100%
Updates
Times in UTCAs posted by Scaleway
The interlink router at DC3 experienced an underlay connectivity issue, potentially impacting customers connected to this router. As a result, affected customers may have experienced a disruption to their production traffic for approximately 4 minutes.
Scaleway in the last 90 days
Full historyIncidents in 90 days
70
Days with an incident
36
Median duration
16 h 45 min
This incident
97% shorter than the median
Other Scaleway incidents
All incidentsScaleway·[WEBHOSTING] [fr-par] pf-1010.whm.fr-par.scw.cloud
Scaleway reports that the MySQL service on pf-1010.whm.fr-par.scw.cloud in the fr-par region does not work. Scaleway identified the problem. A rollback with a backup is in progress.
Scaleway·[DOMAIN - DNS] - ns0.online.net and ns0.dom.scw.cloud down
Scaleway reports that DNS resolution does not work on the nameservers ns0.online.net and ns0.dom.scw.cloud over IPv4. The Domains components and the Dedibox and Elements Domains products are affected. Scaleway resolved the incident after 14 minutes.
Scaleway·[COCKPIT] - it-mil - data write/read path KO
From 13:00 CEST to 15:22 CEST: query/write on DS external degraded query on SCW DS degraded
Scaleway·[COCKPIT] - fr-par - Grafana access issues
Scaleway reports that Grafana access issues affected Cockpit in the fr-par region. Scaleway reports that the incident is resolved, and it lasted about 21 hours.
Scaleway·[Dedibox VPS] - VPS provisioning failed
Scaleway reports delays in the provisioning of Dedibox VPS. Scaleway identified the problem and is working on a fix.
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