[Managed database] - [AMS] - New instances can't be provisioning
ResolvedOfficial update
This incident has been resolved.
The latest update from Scaleway.
State
Resolved
Started
5 d ago
2026-10-27 16:32 UTC
Lasted
1 min
until 2026-10-27 16:33 UTC
Worst impact
Notice
Timeline
3 updates16:3216:3216:3316:3316:33
NoticeUpdate postedTimes in UTC
Investigating
1 min 95%
Resolved
1 min 5%
Updates
Times in UTCAs posted by Scaleway
Resolved2026-10-27 16:33 UTC
This incident has been resolved.
Investigating2026-10-27 16:33 UTC
We are continuing to investigate this issue.
Investigating2026-10-27 16:32 UTC
Since 14:51 UTC, new RDB instance can't be provisioning in AMS
Affected components
8nl-ams-1nl-ams-2nl-ams-3DatabasesElements - AZ - nl-ams-1Elements - AZ - nl-ams-2Elements - AZ - nl-ams-3Elements - Products - Databases
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.cc/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.cc/feed.xml?providers=scalewaySlack
/feed subscribe https://outages.cc/feed.xml?providers=scalewayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane