outages.live
Live
ScalewayIncident ·

[VPS] - Paris - servers stuck in maintenance

DegradedOfficial update
0

Scaleway reports that some Dedibox VPS instances in Paris are stuck in the vps.states.maintenance status. The Dedibox VPS product is degraded. Scaleway is investigating the issue.

State

Investigating

Started

Ongoing for

1 h 8 min

Worst impact

Degraded

Timeline

1 update
09:4009:5710:1410:3110:48
DegradedUpdate postedTimes in UTC

Investigating

1 h 8 min 100%

Updates

Times in UTC

As posted by Scaleway

Investigating

Some VPS instances are currently stuck in the “vps.states.maintenance” status. We are currently investigating the issue.

Affected components

2
Dedibox VPSDedibox - Products - Dedibox VPS

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

77

Days with an incident

39

Median duration

7 h 41 min

This incident

85% shorter than the median

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

23 days
median 7 h 41 min
90 days agoToday

Other Scaleway incidents

All incidents

Scaleway·[Transactional Email] - world - Delayed email delivery to Microsoft domains (Outlook/Hotmail)

Scaleway reports delayed email delivery to Microsoft consumer domains, including Outlook and Hotmail. Transactional Email sending pools are affected, and some emails can take up to 1 hour to arrive. Scaleway has identified the cause as an external Microsoft 365 outage, and the incident is still ongoing.

Degraded

Scaleway·[Network] [DC3]- Room S45 rack D14 - Public switch reboot

The public network switch in room S45, rack D14 at Scaleway DC3 is not available. Dedibox services in DC3 have degraded connectivity. Scaleway has identified the problem and replaces the switch.

Degraded

Scaleway·[Network] [DC3]- Room S45 rack D14 - Public switch reboot

At 2026-11-12 16:53:02 CET, the public switch in DC3 room S45 rack D14 rebooted. All servers attached to it have lost public connectivity for approximately 10 mins.

Resolved

Scaleway·[Containers/Functions] - [fr-par] - private endpoints might not be available

Scaleway reports that private endpoints were not available for a subset of Serverless Containers and Serverless Functions in the fr-par region. This affected fr-par-1, fr-par-2 and fr-par-3. The incident is resolved and lasted about 1 hour and 30 minutes.

Resolved

Scaleway·[Generative-Apis] [fr-par] - mistral-small-3.2-24b-instruct-2506 outage

[11/12 - 9:45 UTC+1] The incident has been mitigated, service is back to normal

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