outages.live
Live
ScalewayIncident · 2026-11-02 14:42 UTC

[BILLING] - Billing consumptions in November are not up-to-date

NoticeOfficial update
0

Scaleway billing is not up to date. The problem affects November consumptions in the billing console and the billing APIs. Scaleway reports that the incident is under investigation.

State

Investigating

Started

2 h ago

2026-11-02 14:42 UTC

Ongoing for

2 h 25 min

Worst impact

Notice

Timeline

1 update
14:4215:1915:5516:3117:07
NoticeUpdate postedTimes in UTC

Investigating

2 h 25 min 100%

Updates

Times in UTC

As posted by Scaleway

Investigating2026-11-02 14:45 UTC

November consumptions are not up to date in billing console and billing APIs. We are working at resolving this issue.

Affected components

2
BillingElements - Products - Billing

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

54

Days with an incident

28

Median duration

15 h 5 min

This incident

84% shorter than the median

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

18 days
median 15 h 5 min
90 days agoToday

Other Scaleway incidents

All incidents

Scaleway·[NETWORK] - [DC5] RPN switch is down on DC5/S9/C52

Scaleway reports that the RPN switch on DC5/S9/C52 is down, which affects the RPN service and DC5 rack S9/C52. Scaleway fixed the switch with a cold reboot. The incident is resolved and lasted about two hours and thirty-five minutes.

Resolvedresolved 4 h ago

Scaleway·[Generative APIs] Model mistral-small-3.2-24b-instruct-2506 unavailable.

01/11/2026 - 21:00 UTC+1 - Service started to be degradated 02/11/2026 - 2:00 UTC+1 - Service was unavailable 02/11/2026 - 9:00 UTC+1 - A fix has been implemented, service is available

Resolvedresolved 9 h ago

Scaleway·[Container Registry] FR-PAR API unreacheable upstream request timeout.

Between 8:00 PM and 9:30 PM, requests to the Container Registry API in the FR-PAR region returned the following error: “Upstream request timeout.”

Resolvedresolved 20 h ago

Scaleway·[fr-par] [Serverless SQL DB] Backups will be suspended on Friday and Saturday nights

Scaleway Serverless SQL DB backups do not run in the fr-par region. Scaleway identified the problem and suspended these backups on Friday and Saturday nights. The incident is resolved and lasted 3 days.

Resolvedresolved 3 h ago

Scaleway·[NL-AMS] - 20% of client requests failed with HTTP 503 errors

October 28, 2026 – 16:14 to 16:27 UTC Approximately 20% of Serverless Containers requests in nl-ams returned HTTP 503 errors, and some active client connections may have been interrupted.

Resolvedresolved 4 d ago

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