outages.live
Live
ScalewayMaintenance ·

[Scheduled] [WebHosting Elements] - Platform pf-013

MaintenanceOfficial update

Maintenance for database server update (MySQL 8.4). Websites using a MySQL database will be unavailable for up to 60 minutes during the maintenance.

The latest update from Scaleway.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Scaleway

Scheduled

Maintenance for database server update (MySQL 8.4). Websites using a MySQL database will be unavailable for up to 60 minutes during the maintenance.

Affected components

2
Web HostingElements - Products - Web Hosting

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

62

Days with an incident

32

Median duration

16 h 45 min

This incident

Not comparable

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

18 days
median 16 h 45 min
90 days agoToday

Other Scaleway incidents

All incidents

Scaleway·[DEDIBOX] - RPNv1 network unavailability in DC3 room 4-4 corridors C and D

Scaleway reports RPNv1 network unavailability in DC3, room 4-4, corridors C and D. Scaware says it identified the problem, and the first router is back online. Service should return gradually while teams continue work.

Degraded

Scaleway·[DC3] Switch issues in room 4-4 rack B14 / B15

Scaleway reports that a switch is unavailable in room 4-4, rack B14 and B15, in the DC3 datacenter. This affects Dedibox services in DC3. Scaleway replaced the switch in B14 and put a fix in place. Scaleway monitors the result now.

Degraded

Scaleway·[Transactionnal Email] - Delivering Issue

Scaleway Transactional Email had a delivering issue. Some emails got stuck while processing or sending. Scaleway reports that the incident is resolved and that it lasted about 3 hours and 6 minutes.

Resolved

Scaleway·[Serverless Functions/Containers] - [nl-ams] - Connectivity issues

Scaleway Serverless Containers in the nl-ams region did not work correctly. Some users got HTTP 5xx errors, some containers stayed in creating or updating status, and some containers with VPC support lost connectivity to Private Network resources. Scaleway reports that the incident is resolved. It lasted about 4 hours and 29 minutes.

Resolved

Scaleway·CKPT (pl-waw) Traces ingestion is degraded

Cockpit traces ingestion is degraded on pl-waw. The Cockpit product is affected. Scaleway reports that this incident is resolved. The outage lasted about 158 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