Live

[Cockpit] [fr-par] Partial unavailability of Scaleway metrics ingestion and queries

0

Scaleway metrics ingestion and queries do not work correctly for some clients in the fr-par region, which affects Cockpit and the fr-par-1, fr-par-2 and fr-par-3 zones. Scaleway reports that a fix is in place and the situation is monitored. Scaleway states that custom metrics are not affected.

State

Monitoring

Started

Ongoing for

31 min

Worst impact

Degraded

Timeline

1 update
16:1716:2516:3216:4016:47
DegradedUpdate postedTimes in UTC

Monitoring

31 min 100%

Updates

Times in UTC

As posted by Scaleway

Monitoring

Since 02:30 PM, some clients may have experienced degraded performance when ingesting and querying Scaleway metrics in the FR-PAR region. Ingestion disruption may have resulted in small data gaps, with some metrics missing for a subset of affected clients. Custom metrics are not impacted. A fix has been implemented and we are monitoring the situation

Affected components

8
fr-par-1fr-par-2fr-par-3CockpitElements - AZ - fr-par-1Elements - AZ - fr-par-2Elements - AZ - fr-par-3Elements - Products - Cockpit

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

97% 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