[Managed Database] - MongoDB - Important security and stability update
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from Scaleway.
State
In progress
Started
Ongoing for
46 min
Worst impact
Maintenance
Timeline
2 updatesScheduled
1 min 3%
In progress
45 min 97%
Updates
Times in UTCAs posted by Scaleway
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Impact Instance restart: a few seconds (clusters), up to 1 minute (standalone). Forced Maintenance Window November 13, before 12:00 PM CET: the affected instances will be upgraded during this window. Customer action: No action is possible on customer side
Affected components
2Scaleway in the last 90 days
Full historyIncidents in 90 days
77
Days with an incident
39
Median duration
10 h 33 min
This incident
Not comparable
Other Scaleway incidents
All incidentsScaleway·[VPS] - Paris - servers stuck in maintenance
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.
Scaleway·[Transactional Email] - world - Delayed email delivery to Microsoft domains (Outlook/Hotmail)
Scaleway Transactional Email has delayed delivery to Microsoft consumer domains such as Outlook and Hotmail. All sending pools are affected. Scaleway has identified the cause as a Microsoft 365 and Exchange Online outage. Scaleway now refuses email to Microsoft servers with a 550 5.7.1 SMTP message, and cancelled or bounced emails can be resent after Microsoft services recover.
Scaleway·[Network] [DC3]- Room S45 rack D14 - Public switch reboot
Scaleway reports a public switch reboot in room S45, rack D14 at DC3. This issue affects Dedibox public connectivity in DC3. Scaleway resolved the incident after 18 hours and 52 minutes.
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.
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.
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