[Cockpit] [fr-par] Partial unavailability of Scaleway metrics ingestion and queries
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 updateMonitoring
31 min 100%
Updates
Times in UTCAs posted by Scaleway
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
8Scaleway in the last 90 days
Full historyIncidents in 90 days
83
Days with an incident
44
Median duration
16 h 59 min
This incident
97% shorter than the median
Other Scaleway incidents
All incidentsScaleway·[RDB] - Public and private endpoint are not correctly displayed in the console
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.
Scaleway·[APPLE SILICON] - FR-PAR-1 - Macs cannot reach Scaleway public API
Apple Silicon Macs in fr-par-1 cannot reach the Scaleway public API. Scaleway reports that it is investigating the incident. Scaleway advises customers to avoid a reinstall or a reboot of the Macs at this time.
Scaleway·[GENERATIVE API] - [GLOBAL] - Increased error rate for model DeepSeek v4.1 Flash 1017
Scaleway reports more errors for the model DeepSeek v4.1 Flash 1017. The Generative API is degraded. Scaleway is investigating the problem.
Scaleway·[IAM] - Cannot add or update organization-level policy rules
Scaleway reports that users cannot add or update IAM policy rules with organization-level permission sets. The incident is resolved. It lasted 67 minutes.
Scaleway·[Generative API] - [global] - GLM-5.3 timeouts
Scaleway reports that requests to the GLM-5.3 model in the Generative API returned timeout errors globally. Scaleway reports that this incident is resolved after 43 hours and 3 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