Live

[RDB] - Public and private endpoint are not correctly displayed in the console

0

Scaleway reports a display fault in the console for Managed Database instance endpoints. Public endpoints can show as unavailable, but they stay active and reachable. Scaleway is investigating this display-only issue.

State

Investigating

Started

Ongoing for

17 min

Worst impact

Degraded

Timeline

1 update
16:3016:3516:3916:4316:47
DegradedUpdate postedTimes in UTC

Investigating

17 min 100%

Updates

Times in UTC

As posted by Scaleway

Investigating

The console may incorrectly display Managed Database instance endpoints: public endpoints can appear as unavailable, even though they remain active and reachable. This is a display-only issue in the console interface. All endpoints continue to function normally, and the RDB API returns accurate information. No action is required on your part.

Affected components

2
Managed InferenceElements - Products - Managed Inference

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

83

Days with an incident

44

Median duration

16 h 59 min

This incident

98% shorter than the median

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

28 days
median 16 h 59 min
90 days agoToday

Other Scaleway incidents

All incidents

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