Live

[Generative API] - [global] - GLM-5.3 timeouts

0

Scaleway reports that the glm-5.3 model returns timeout errors on requests. This affects the Generative API and the Elements Generative API product. Scaleway is investigating the issue and works to fix it.

State

Investigating

Started

Ongoing for

20 h 44 min

Worst impact

Degraded

Timeline

1 update
14:0619:1700:2805:3810:49
DegradedUpdate postedTimes in UTC

Investigating

20 h 44 min 100%

Updates

Times in UTC

As posted by Scaleway

Investigating

The glm-5.3 model is returning timeout errors on requests. We are working at fixing the issue.

Affected components

2
Generative APIElements - Products - Generative API

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

78

Days with an incident

43

Median duration

16 h 45 min

This incident

1.2× the median

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

27 days
median 16 h 45 min
90 days agoToday

Other Scaleway incidents

All incidents

Scaleway·[VPS] - Paris - servers stuck in maintenance

Scaleway Dedibox VPS instances in Paris do not work when they stay in the vps.states.maintenance status. Scaleway reports that the incident is resolved. The incident lasted from 13 November 2026 to 16 November 2026.

Resolved · 1 affected

Scaleway·[Transactional Email] - world - Delayed email delivery to Microsoft domains (Outlook/Hotmail)

Scaleway Transactional Email delivery to Microsoft consumer domains (Outlook and Hotmail) was delayed. All sending pools were affected. Scaleway reported the incident as resolved on 2026-11-16. The incident lasted about 3 days and 14 hours.

Resolved

Scaleway·[Network] [DC3]- Room S45 rack D14 - Public switch reboot

Scaleway reports a public switch reboot in room S45, rack D14 at DC3. This issue affects Dedibox public connectivity in DC3. Scaleway resolved the incident after 18 hours and 52 minutes.

Resolved

Scaleway·[Network] [DC3]- Room S45 rack D14 - Public switch reboot

At 2026-11-12 16:53:02 CET, the public switch in DC3 room S45 rack D14 rebooted. All servers attached to it have lost public connectivity for approximately 10 mins.

Resolved

Scaleway·[Containers/Functions] - [fr-par] - private endpoints might not be available

Scaleway reports that private endpoints were not available for a subset of Serverless Containers and Serverless Functions in the fr-par region. This affected fr-par-1, fr-par-2 and fr-par-3. The incident is resolved and lasted about 1 hour and 30 minutes.

Resolved

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