outages.live
Live
ScalewayIncident · 2026-10-27 11:03 UTC

[Generative APIs] - GLM-5.3 model unavailability

ResolvedOfficial update

This incident has been resolved.

The latest update from Scaleway.

State

Resolved

Started

5 d ago

2026-10-27 11:03 UTC

Lasted

47 h 46 min

until 2026-10-29 10:49 UTC

Worst impact

Degraded

Timeline

2 updates
Oct 27Oct 27Oct 28Oct 28Oct 29
DegradedUpdate postedDates in UTC

Investigating

47 h 46 min 100%

Updates

Times in UTC

As posted by Scaleway

Resolved2026-10-29 10:49 UTC

This incident has been resolved.

Investigating2026-10-27 11:03 UTC

[10:06] Requests on model had experienced elevated timeouts. [10:15] Model has been unavailable [10:50] Fix has been applied

Affected components

2
Generative APIElements - Products - Generative API

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

50

Days with an incident

27

Median duration

17 h 50 min

This incident

2.7× the median

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

18 days
median 17 h 50 min
90 days agoToday

Other Scaleway incidents

All incidents

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. The impact is degraded on Serverless-Database components. Scaleway identified the cause and suspended backups on Friday and Saturday nights. Backups start again on Monday morning.

Degradedupdated 2 d 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 3 d ago

Scaleway·[fr-par-1] Latencies spikes during the day following capacity increase in one of block storage cluster

Scaleway Block Storage has latency spikes in the fr-par-1 region. This degrades Block Storage, Databases, and Instances. Scaleway identified the problem and applies a fix rack by rack. Data must be removed first, so migrations run slowly and continue through the weekend.

Degradedupdated 2 d ago

Scaleway·[fr-par] [Serverless SQL DB] All SQL databases are unavailable

This incident has been resolved.

Resolvedresolved 2 d ago

Scaleway·[TEM] - TEM IP address blacklist

The IP address 51.159.124.109 has been blacklisted by Spamhaus. It is possible that some emails may still be rejected if this listing is cached. The incident for this IP address lasted from: Date Listed: October 28, 2026, 6:46:49 PM Date Removed: October 28, 2026, 8:54:39 PM

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.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=scaleway
Slack
/feed subscribe https://outages.cc/feed.xml?providers=scaleway

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane