outages.live
Live
ScalewayMaintenance ·

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

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

64

Days with an incident

33

Median duration

13 h 24 min

This incident

Not comparable

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

18 days
median 13 h 24 min
90 days agoToday

Other Scaleway incidents

All incidents

Scaleway·[Block Storage] - fr-par-1 - Write latency increase due to background operations

Since 22:00 UTC, write latency increased on one Block Storage cluster in fr-par-1 because of background operations. The issue is resolved. Write latency on this cluster returned to normal at 11:28 UTC, about 4 hours after Scaleway identified the problem.

Resolved

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. This affects multiple racks. Scaleway implemented a fix and now monitors the results.

Degraded

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

Scaleway reports switch issues in room 4-4, rack B14 and B15, at its DC3 datacenter. These issues degrade Dedibox services in DC3. Scaleway replaced the switch in B14, put a fix in place, and now monitors the results.

Degraded

Scaleway·[Transactionnal Email] - Delivering Issue

Scaleway Transactional Email had a delivering issue that affected some emails in the Elements products. Scaleway identified the issue and restored outbound traffic. The incident is resolved and lasted about 3 hours and 6 minutes.

Resolved

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

Scaleway Serverless Containers in the nl-ams region had connectivity problems. Some containers returned HTTP 5xx errors, were stuck in creating or updating, or lost Private Network connectivity. Scaleway reports the incident resolved. It lasted about 4 hours and 29 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.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