Live

[DC5] Public switch issue in DC5; room 1 ; Rack C20

0

A public switch problem in DC5, room 1, rack C20 affects Dedibox connectivity. Scaleway reports the status as investigating. Scaleway technical teams troubleshoot to restore service.

State

Investigating

Started

Ongoing for

1 h 18 min

Worst impact

Degraded

Timeline

1 update
07:5708:1608:3508:5509:14
DegradedUpdate postedTimes in UTC

Investigating

1 h 18 min 100%

Updates

Times in UTC

As posted by Scaleway

Investigating

A problem has been detected with a network switch, Rack C20 - Datacenter [DC5] causing connectivity loss. Our technical teams are actively troubleshooting to restore service.

Affected components

4
DediboxDC5Dedibox - Datacenters - DC5Dedibox - Products - Dedibox

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

86

Days with an incident

46

Median duration

17 h 12 min

This incident

92% shorter than the median

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

30 days
median 17 h 12 min
90 days agoToday

Other Scaleway incidents

All incidents

Scaleway·[Network] [nl-ams] Backbone connectivity issue from Amazon to Scaleway nl-ams

Scaleway reports degraded backbone connectivity from Amazon to the nl-ams region. This affects the nl-ams-1, nl-ams-2 and nl-ams-3 availability zones and the Network product. Scaleway is investigating the issue with Amazon.

Degraded

Scaleway·[Block Storage] - [fr-par-1] - Write latencies increased overnight

Block Storage write latencies increased in fr-par-1. Scaleway identified the problem and reported that latencies returned to normal. The incident is resolved and lasted 70 minutes.

Resolved

Scaleway·[MANAGED DATABASE] - Public and private endpoint are not correctly displayed in the console

Scaleway reports a display problem in the console for Managed Database public and private endpoints. The public endpoints can appear as unavailable. The incident is resolved and lasted about 21 hours and 29 minutes.

Resolved

Scaleway·[Cockpit] [fr-par] Partial unavailability of Scaleway metrics ingestion and queries

Scaleway metrics ingestion and queries are degraded in the FR-PAR region, which affects Cockpit and availability zones fr-par-1, fr-par-2, and fr-par-3. Some clients may have dropped metrics; custom metrics are not impacted. Scaleway reports that a fix is implemented and the situation is under monitoring.

Degraded

Scaleway·[APPLE SILICON] - FR-PAR-1 - Macs cannot reach Scaleway public API

Scaleway Apple Silicon Macs in fr-par-1 cannot reach the Scaleway public API. Scaleway says the problem is identified and is in the network devices that connect the Macs. Scaleway tested a fix and plans to push it in fr-par-1 globally.

Partial outage

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