P2 - [WEBHOSTING] - PHP Emergency maintenance
Scaleway reports an emergency PHP maintenance on Hosting, Web Hosting, Dedibox Hosting and Web Hosting Elements. Scaleway identified the problem. Patched PHP versions 5.6 to 7.3 are deployed on all Classic shared hosting, and those websites are back online. PHP 4 websites stay in maintenance. Customers can move these websites to PHP 5.6 or later.
State
Identified
Started
11 d ago
2026-10-21 14:38 UTC
Ongoing for
11 days
Worst impact
Major outage
Timeline
1 updateIdentified
11 days 100%
Updates
Times in UTCAs posted by Scaleway
[Update] Security Maintenance – Web Hosting Services Classic Shared Hosting / Mutu (Back online): Patched PHP versions (5.6, 7.0, 7.1, 7.2 and 7.3) have been fully deployed across all Classic shared hosting environments, and maintenance mode has been lifted. Websites are back online, except PHP 4 which remains in maintenance. Current behavior per PHP version: -PHP 7.x: websites are served normally on their patched PHP version. -PHP 5.x: websites previously running PHP 5.2, 5.4 or 5.5 have been automatically migrated to PHP 5.6 (patched) and are served normally. We recommend that customers check that their websites are working correctly after this version change, following the recommendations in this guide: https://www.scaleway.com/en/docs/webhosting/reference-content/php-5-6-migration-guide/ -PHP 4: websites remain in maintenance and are served a maintenance page. Customers can bring their websites back online by migrating to PHP 5.6 or later. We apologize for the inconvenience, and th
Affected components
4Scaleway in the last 90 days
Full historyIncidents in 90 days
51
Days with an incident
28
Median duration
16 h 45 min
This incident
16× the median
Other Scaleway incidents
All incidentsScaleway·[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.”
Scaleway·[fr-par] [Serverless SQL DB] Backups will be suspended on Friday and Saturday nights
Backups do not run for Serverless SQL DB in the fr-par region on Friday nights and Saturday nights. Scaleway reports the cause as identified. Backup runs start again on Monday morning.
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.
Scaleway·[fr-par-1] Latencies spikes during the day following capacity increase in one of block storage cluster
Scaleway reports latency spikes on Block Storage, Databases, and Instances in the fr-par-1 region. Scaleway identified the problem and applies a fix rack by rack. Data moves slowly to limit more latency, and the work continues through the weekend.
Scaleway·[fr-par] [Serverless SQL DB] All SQL databases are unavailable
This incident has been 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.
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.
https://outages.live/feed.xml?providers=scaleway/feed subscribe https://outages.live/feed.xml?providers=scalewayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane