outages.live
Live
ScalewayIncident · 2026-10-22 15:18 UTC

[Serverless Functions][fr-par/nl-ams/pl-waw] Security updates applied to PHP and Node.js runtimes

ResolvedOfficial update

This incident has been resolved.

The latest update from Scaleway.

State

Resolved

Started

10 d ago

2026-10-22 15:18 UTC

Lasted

51 min

until 2026-10-22 16:10 UTC

Worst impact

Degraded

Timeline

3 updates
15:1815:3115:4415:5716:10
DegradedUpdate postedTimes in UTC

Investigating

10 min 19%

Monitoring

42 min 81%

Updates

Times in UTC

As posted by Scaleway

Resolved2026-10-22 16:10 UTC

This incident has been resolved.

Monitoring2026-10-22 15:28 UTC

A fix has been implemented and we are monitoring the results.

Investigating2026-10-22 15:18 UTC

We are informing you of critical security updates applied to the PHP and Node.js runtimes used by Serverless Functions. --- PHP Two critical vulnerabilities (CVE-2026-109618 and CVE-2026-109619, CVSS 9.2) allow remote code execution without credentials on PHP versions prior to the fixed releases (8.2.35, 8.3.36, 8.4.27, 8.5.12). Actions taken: - Functions previously running PHP 8.2 or 8.3 have been force-redeployed on PHP 8.4, which is patched. - Functions running PHP 8.4 or 8.5 have been force-redeployed on the patched versions (8.4.27 / 8.5.12). Impact for you: - PHP 8.2 and 8.3 are now end-of-life on our platform: they can no longer be used to create or redeploy functions. Please update your runtime to PHP 8.4 or 8.5. - If you manage your functions through Infrastructure as Code (Terraform or Serverless Framework with serverless.yaml), please update your configuration to the new runtime, otherwise your infrastructure will drift. --- Node.js Patched versions of Node.js 22, 24 and 26

Affected components

20
fr-par-1fr-par-2fr-par-3nl-ams-1nl-ams-2nl-ams-3pl-waw-1pl-waw-2

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

51

Days with an incident

28

Median duration

16 h 45 min

This incident

95% shorter than the median

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·[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.”

Resolvedresolved 5 h ago

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.

Degradedupdated 3 d ago

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.

Resolvedresolved 4 d ago

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.

Degradedupdated 2 d ago

Scaleway·[fr-par] [Serverless SQL DB] All SQL databases are unavailable

This incident has been resolved.

Resolvedresolved 3 d ago

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