outages.live
Live
ScalewayIncident ·

[DOMAIN - DNS] - ns0.online.net and ns0.dom.scw.cloud down

ResolvedOfficial update
0

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.

State

Resolved

Started

Lasted

14 min

Worst impact

Notice

Timeline

2 updates
16:4916:5316:5616:5917:03
NoticeUpdate postedTimes in UTC

Investigating

14 min 100%

Updates

Times in UTC

As posted by Scaleway

Resolved
Investigating

We are experiencing a DNS resolution issue affecting the following nameservers over IPv4 only : ns0.online.net and ns0.dom.scw.cloud.

Affected components

3
DomainsDedibox - Products - DomainsElements - Products - Domains

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

68

Days with an incident

36

Median duration

7 h 41 min

This incident

97% shorter than the median

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

20 days
median 7 h 41 min
90 days agoToday

Other Scaleway incidents

All incidents

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

Resolved

Scaleway·[COCKPIT] - fr-par - Grafana access issues

Scaleway reports that Grafana access in Cockpit does not work for some users in the fr-par region. This affects Cockpit and Elements - Products - Cockpit. Scaleway states the problem is fixed and is now under monitoring.

Degraded

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.

Degraded

Scaleway·[Network infrastructure] - AMS1 ; Room H6 Rack 50 - RPN Switch down

The RPN switch in room H6 rack 50 in the AMS1 region is down. RPN connectivity is not available for some servers in this rack. Scaleway reports that the incident is resolved, and it lasted 38 minutes.

Resolved

Scaleway·[Block Storage] - fr-par-1 - Write latency increase due to background operations

Scaleway Block Storage write latency increased in fr-par-1. The problem affected one Block cluster and started at 22:00 UTC. Scaleway reports that the incident is resolved. Write latencies returned to normal after about 4 hours.

Resolved

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