Degraded / minor incident Scaleway status
scaleway.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Scaleway's status page shows “Degraded / minor incident” in Hosting and Web Hosting; the vendor is identified the cause. User reports haven't spiked, so wide impact isn't visible yet.
confidence: low Vendor: minor issue · users: normal · routing: normal.
- Vendor status page Degraded / minor incident · 5 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS12876 prefixes seen by 100% of RIPE RIS peers
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Hosting, Web Hosting, fr-par-1
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 30 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 15 h 8 min |
Evidence
- Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
- Vendor stage: identified the cause on “P2 - [WEBHOSTING] - PHP Emergency maintenance”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- AS12876 prefixes seen by 100% of RIPE RIS peers. evidence confidence: medium
What we don't know: what is happening inside Scaleway's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “identified the cause”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: normal. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
We don't map other services that depend on Scaleway. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Scaleway, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; routing visibility returning to normal; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Scaleway. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
P2 - [WEBHOSTING] - PHP Emergency maintenance
critical identified · started
4 updates
- identified
The PHP project released today a fix for two critical vulnerabilities allowing unauthenticated remote code execution (CVE-2026-109618, CVE-2026-109619, CVSS 9.2 — no complete mitigation exists): https://www.php.net/archive/2026.php#2026-10-21-5 As a precaution, we have taken Webhosting websites offline while we apply the patched PHP versions. Our team is actively working to patch and restore the service as soon as possible.
- identified
[Update] Security Maintenance – Web Hosting Services Security patching for the php2shell vulnerability is progressing: cPanel Environments (Resolved): PHP versions have been updated across all Scaleway and Online.net cPanel servers (as well as Scaleway Plesk). Maintenance mode has been lifted, and services are back online. Classic Shared Hosting / Mutu (In Progress): Classic shared environments remain under maintenance while work is actively underway.
- identified
[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 the
- identified
PHP 4 websites: migration to PHP 5.6 in progress To protect all hosted websites, we are migrating the remaining PHP 4 websites to PHP 5.6 (patched). This migration will be completed by the end of the day, after which the maintenance page will be lifted and these websites will be served again on PHP 5.6. Websites made only of static HTML pages do not use PHP: they were not affected by the maintenance and are not affected by this migration. For PHP-based websites, we strongly recommend checking that they are working correctly after the migration, following the recommendations in this guide: https://www.scaleway.com/en/docs/webhosting/reference-content/php-5-6-migration-guide/ Thank you for your understanding and patience throughout this maintenance.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.