Scaleway Outage History

Scaleway degraded · 4 active incidents · 2 long-running issues View live status →

Pingoru has recorded 361 incidents for Scaleway: 360 in the last 12 months and 131 in the last 90 days.

Source: status.scaleway.com

361incidents recorded
360last 12 months
131last 90 days
3 daystypical duration
Incidents per month
050100AprMayJunJulAugSepOct42
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct100%
Pingoru began tracking Scaleway in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202636646 of 720 (90%)
May 202645723 of 744 (97%)
June 202660575 of 720 (80%)
July 202665654 of 744 (88%)
August 202634572 of 744 (77%)
September 202647720 of 720 (100%)
October 202642532 of 532 (100%)

Incidents, newest first

Minor October 22, 2026 [Serverless Functions][fr-par/nl-ams/pl-waw] Security updates applied to PHP and Node.js runtimes 51m fr-par-1, fr-par-2, fr-par-3, nl-ams-1 and 6 more

Started Oct 22, 2026, 03:18 PM UTC· resolved Oct 22, 2026, 04:10 PM UTC

  1. investigating Oct 22, 2026, 03:18 PM 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 are now available (22.23.4, 24.22.1, 26.12.1). To apply the security patches, please redeploy your functions. If you experience any issue, please contact our support team. We apologize for any inconvenience and thank you for your patience.

  2. monitoring Oct 22, 2026, 03:28 PM UTC

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

  3. resolved Oct 22, 2026, 04:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 21, 2026 [GAPI] - [global] - Dedicated deployment deletion failing 13h 24m Generative API

Started Oct 21, 2026, 06:05 PM UTC· resolved Oct 22, 2026, 07:30 AM UTC

  1. investigating Oct 21, 2026, 06:05 PM UTC

    Since 7 pm, dedicated deployment deletion has been failing. Re-creation after deletion will remain impossible until the incident is resolved.

  2. resolved Oct 22, 2026, 07:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 21, 2026 P3 - [INSTANCES] - it-mil-1 - Instance APIs down 2h 25m Instances, VPC

Started Oct 21, 2026, 04:31 PM UTC· resolved Oct 21, 2026, 06:57 PM UTC

  1. identified Oct 21, 2026, 04:31 PM UTC

    Since 16:00 UTC, Instances APIs are unavailable on it-mil-1. This also has some minor impacts on the region: unable to delete a VPC or a project.

Read the full incident report →

Critical October 21, 2026 Emergency Maintenance - Dedibox Console 16h 45m Dedibox, Dedibox Console

Started Oct 21, 2026, 02:37 PM UTC· resolved Oct 22, 2026, 07:22 AM UTC

  1. investigating Oct 21, 2026, 02:37 PM UTC

    Emergency Maintenance in Progress As part of our investigation into the PHP2SHELL vulnerability (CVE), we are placing console.online.net and api.online.net into maintenance mode as a precautionary measure. The entire console is temporarily unavailable. This maintenance affects only the control plane (Dedibox ordering system and management interface). Hosted servers and services are not affected. Your data remains safe. This maintenance is a precautionary measure while we investigate the vulnerability. We will provide an update as soon as the service is restored.

  2. investigating Oct 21, 2026, 09:35 PM UTC

    Investigation and mitigation of the PHP2Shell vulnerability are still ongoing. Your data and dedibox servers remain safe. You can continue to manage Dedibox servers through the Scaleway Console. We will restore the normal service status once maintenance is complete.

  3. resolved Oct 22, 2026, 07:22 AM UTC

    The Dedibox Console and API are now back online and fully operational. The security patches have been successfully applied to mitigate the PHP2Shell vulnerability. Thank you for your patience and understanding.

Read the full incident report →

Critical October 21, 2026 [BookMyName][Security] Emergency maintenance - BMN services unavailable 18h 54m BookMyName

Started Oct 21, 2026, 02:06 PM UTC· resolved Oct 22, 2026, 09:00 AM UTC

  1. investigating Oct 21, 2026, 02:06 PM UTC

    Started: 21 Oct 2026, 15:50 CEST Status: Emergency maintenance in progress Impact: All BMN services are unavailable. 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 BMN services offline while we apply the patched PHP versions. Our team is actively working to patch and restore the service as soon as possible.

  2. identified Oct 21, 2026, 04:51 PM UTC

    Update at 18:40 CEST The BookMyName website, its webmail, and the RDAP services are back up. The redirection service is still down: it requires further investigation before it can be patched and restored.

  3. resolved Oct 22, 2026, 09:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 21, 2026 [Block Storage] [fr-par-2] - Block Storage control plane issue during upgrade 2h

Started Oct 21, 2026, 10:00 AM UTC· resolved Oct 21, 2026, 12:00 PM UTC

  1. resolved Oct 21, 2026, 01:00 PM UTC

    An upgrade operation of the Block storage api on fr-par-2 generated a blocking transaction which impacted the control plane of this AZ The issue occurred from 12:23 to 12:28 UTC and generated a high rate of 500 errors. The problem was quickly fixed by the engineers of the product team.

Read the full incident report →

Minor October 21, 2026 [Generative API] - [global] - New dedicated deployment creation temporarily unavailable 7h 40m Generative API

Started Oct 21, 2026, 09:20 AM UTC· resolved Oct 21, 2026, 05:00 PM UTC

  1. monitoring Oct 21, 2026, 09:20 AM UTC

    New deployment creation is temporarily unavailable due to infrastructure capacity constraints. Existing deployments are unaffected. We're actively monitoring the situation.

  2. identified Oct 21, 2026, 09:24 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Oct 21, 2026, 05:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 21, 2026 [Cockpit] (fr-par) custom logs datasources were partially unavailable for writing and querying 23h

Started Oct 21, 2026, 08:44 AM UTC· resolved Oct 22, 2026, 07:45 AM UTC

  1. resolved Oct 21, 2026, 08:44 AM UTC

    * 2026-10-20 17:45 CEST : Partial unavailability of custom logs datasource * 2026-10-20 18:00 CEST : mitigation deployed, stabilizing availability progressively * 2026-10-21 05:00 CEST : automated event happened, which triggered partial unavailability again for part of our customers. * 2026-10-21 09:45 CEST : stabilization of our infrastructure, back to nominal situation

Read the full incident report →

Minor October 20, 2026 [IAM] Some users experienced login issues with SAML authentication – IAM

Started Oct 20, 2026, 03:37 PM UTC· resolved Oct 20, 2026, 03:37 PM UTC

  1. resolved Oct 20, 2026, 03:37 PM UTC

    Users signing in with SAML who had not yet configured MFA were unable to log in. The issue was caused by a recent frontend release. A fix has been implemented, and an updated version of the account app is being deployed.

Read the full incident report →

Minor October 20, 2026 [fr-par] Partial unavailability affecting an Object Storage cluster 21h 2m fr-par-1, fr-par-2, fr-par-3, Object Storage

Started Oct 20, 2026, 03:21 PM UTC· resolved Oct 21, 2026, 12:23 PM UTC

  1. identified Oct 20, 2026, 03:21 PM UTC

    Following a network deployment, several racks have lost their network access, this is creating some errors and latencies, we identified the problem and are deploying a fix right now.

  2. identified Oct 20, 2026, 03:27 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Oct 20, 2026, 03:48 PM UTC

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

  4. monitoring Oct 20, 2026, 04:13 PM UTC

    Object Storage services in the fr-par region have returned to normal operating conditions following the deployment of the fix. Our teams continue to closely monitor the infrastructure to ensure service stability before marking the incident as resolved.

  5. resolved Oct 21, 2026, 12:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2026 [Generative API] - [global] - Bge-multilingual-gemma-2 became unavailable 23m Generative API

Started Oct 20, 2026, 01:59 PM UTC· resolved Oct 20, 2026, 02:23 PM UTC

  1. investigating Oct 20, 2026, 01:59 PM UTC

    Started Tuesday 20th October 2:50pm The model is not available. We're working to fix it asap.

  2. resolved Oct 20, 2026, 02:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2026 [Cockpit] Listing data exporters results in an error 21h 37m fr-par-1, fr-par-2, fr-par-3, nl-ams-1 and 9 more

Started Oct 20, 2026, 10:12 AM UTC· resolved Oct 21, 2026, 07:50 AM UTC

  1. investigating Oct 20, 2026, 10:12 AM UTC

    After a faulty deployment, listing data exporters in the Cockpit Console results in error.

  2. resolved Oct 21, 2026, 07:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 19, 2026 [Generative API] - [global] - Deepseek v4.1 flash timeouts 20h Generative API

Started Oct 19, 2026, 05:02 PM UTC· resolved Oct 20, 2026, 01:03 PM UTC

  1. identified Oct 19, 2026, 05:02 PM UTC

    19th October from 2:30pm to 7pm Some requests to the deepseek-v4.1-flash model have experienced elevated timeouts. We have implemented a mitigation, and error rates are improving. We're monitoring the situation.

  2. monitoring Oct 19, 2026, 05:15 PM UTC

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

  3. resolved Oct 20, 2026, 01:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 19, 2026 [Serverless-Database]- [fr-par] - slow cold start for the DB and DB in status error 2h 6m Serverless-Database

Started Oct 19, 2026, 07:45 AM UTC· resolved Oct 19, 2026, 09:52 AM UTC

  1. investigating Oct 19, 2026, 07:45 AM UTC

    Since Saturday October 18, 2026 at 07:55 UTC (09:55 Paris time), Serverless SQL Databases as occured slow cold start for the DB and DB in status error.

  2. resolved Oct 19, 2026, 09:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 19, 2026 [Dedibox] - PARDC3 / Room 4-4 / Rack C18 - PUB switch unreachable 22h 58m Dedibox

Started Oct 19, 2026, 07:30 AM UTC· resolved Oct 20, 2026, 06:28 AM UTC

  1. investigating Oct 19, 2026, 07:30 AM UTC

    PUB service down on devices located in PARDC3 / Room 4-4 / Rack C18 since 2026/10/18 12:30 UTC, Checks in progress

  2. monitoring Oct 19, 2026, 09:10 AM UTC

    A faulty device has been replaced.

  3. resolved Oct 20, 2026, 06:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 19, 2026 [Instances] - AMS1 / Room Hall6 / Rack 6.12.32 - ams1dc1-net-f02lf75.ams1 crashes multiple time 1m Instances

Started Oct 19, 2026, 07:27 AM UTC· resolved Oct 19, 2026, 07:29 AM UTC

  1. identified Oct 19, 2026, 07:27 AM UTC

    An issue on a network device generated instability between 2026/10/17 10:42 UTC and 2026/10/17 10:57 UTC for devices located in rack 6.12.32 room Hall6 in AMS1

  2. identified Oct 19, 2026, 07:28 AM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Oct 19, 2026, 07:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 16, 2026 [FR-PAR-1] - Failure in cooling system 1h 2m fr-par-1, Instances

Started Oct 16, 2026, 05:22 PM UTC· resolved Oct 16, 2026, 06:24 PM UTC

  1. investigating Oct 16, 2026, 05:22 PM UTC

    Servers in room 108 experience temperature increase. This lead to CPU throttling and may result into unreachable instance. We are working with our datacenter provider to fix the situation.

  2. monitoring Oct 16, 2026, 05:43 PM UTC

    Temperatures are decreasing following an intervention by our service provider.

  3. resolved Oct 16, 2026, 06:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 16, 2026 [GAPI] - [Global] - Qwen3 Embeddings produces timeouts 29m Generative API

Started Oct 16, 2026, 01:22 PM UTC· resolved Oct 16, 2026, 01:52 PM UTC

  1. investigating Oct 16, 2026, 01:22 PM UTC

    Timeouts are observed on qwen3-embedding-8b model through the Generative API.

  2. resolved Oct 16, 2026, 01:52 PM UTC

    The incident is now resolved. Customers should not see timeouts anymore. We continue to monitor the related deployments.

Read the full incident report →

Minor October 15, 2026 [DC3] - Public Switch Unreachable at DC3, Rack S46-E16 4d 7h Dedibox, DC3

Started Oct 15, 2026, 08:17 AM UTC· resolved Oct 19, 2026, 03:44 PM UTC

  1. investigating Oct 15, 2026, 08:17 AM UTC

    We are currently experiencing an issue with the public switch located in Rack S46-E16 at Opcore-DC3. The switch is currently unreachable, and the root cause of the issue is still under investigation. As a result, all customer servers connected to this switch are currently unreachable. Our team is investigating the situation and will provide further updates as soon as more information becomes available.

  2. identified Oct 15, 2026, 08:37 AM UTC

    We found the root cause and applied a patch in order to recover the service. However, while further incidents cannot be entirely ruled out, our technical teams are actively working to identify and implement the necessary measures to prevent recurrence.

  3. resolved Oct 19, 2026, 03:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 15, 2026 [Network] [DC2]- Switch Down in Room 205-Rack G2. 4h 23m Dedibox, DC2

Started Oct 15, 2026, 06:03 AM UTC· resolved Oct 15, 2026, 10:26 AM UTC

  1. investigating Oct 15, 2026, 06:03 AM UTC

    We have detected a public switch is down in DC2, Room : 205 205, Rack G2

  2. resolved Oct 15, 2026, 10:26 AM UTC

    1st network device replaced at : 10:38 2nd network device replaced at : 11:58 Issue was due to network device that broke due to a powersurge in the rack

Read the full incident report →

Minor October 13, 2026 [Dedibox] - [DC5] - RPN Switch bay A53 and A54 planned maintenance 1d DC5, RPN

Started Oct 13, 2026, 10:46 AM UTC· resolved Oct 14, 2026, 10:53 AM UTC

  1. investigating Oct 13, 2026, 10:46 AM UTC

    We have a temporary outage on a RPN Switch bay A53 an A54 which might cause traffic issue. As such, a maintenance is planned : 14/10 - 10 AM UTC/12 AM Paris time A short interruption (approximately 5 minutes) is to be expected.

  2. resolved Oct 14, 2026, 10:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 12, 2026 [Dedibox] - [DC5] - Rack D38 of room 1 lost connectivity 19h 53m Dedibox, DC5

Started Oct 12, 2026, 04:46 PM UTC· resolved Oct 13, 2026, 12:40 PM UTC

  1. investigating Oct 12, 2026, 04:46 PM UTC

    We are currently experiencing a network incident affecting a switch in DC5, which is currently unreachable. Our technical team is investigating the situation and working on the required recovery actions.

  2. resolved Oct 13, 2026, 12:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 11, 2026 [DOMAIN-DNS] - DNS synchronization failed 10d 21h Domains

Started Oct 11, 2026, 10:10 AM UTC· resolved Oct 22, 2026, 07:23 AM UTC

  1. investigating Oct 11, 2026, 10:10 AM UTC

    Several reports of inconsistencies in the zones between our DNS servers s0.dom.scw.cloud and s1.dom.scw.cloud

  2. monitoring Oct 11, 2026, 11:04 AM UTC

    Updates had piled up, causing these issues. It has now been resolved.

  3. resolved Oct 22, 2026, 07:23 AM UTC

    The global incident is now solved. If you still experience issues, please reach out our support through usual means.

Read the full incident report →

Minor October 8, 2026 [Jobs] - [fr-par] - Jobs are stuck in a transient state 34m Jobs

Started Oct 08, 2026, 01:38 PM UTC· resolved Oct 08, 2026, 02:13 PM UTC

  1. investigating Oct 08, 2026, 01:38 PM UTC

    [Started Around 14h00 CET] Jobs cannot be executed. Clients will see job runs stuck in transient states like validated, queued, or running. Issue is under investigation

  2. resolved Oct 08, 2026, 02:13 PM UTC

    The issue is resolved. The Jobs API v1alpha1 was not available during incident and clients may have experienced PermissionDenied errors. The Jobs API v1alpha2 was available but job runs were stuck in transient states (validated, queued or running) after start. The Jobs are being executed progressively. Some job runs can take some time to be executed.

Read the full incident report →

Minor October 8, 2026 [Dedibox VPS] [fr-par] - servers locked in Paris location 1h 39m Dedibox VPS

Started Oct 08, 2026, 11:48 AM UTC· resolved Oct 08, 2026, 01:27 PM UTC

  1. investigating Oct 08, 2026, 11:48 AM UTC

    Customers may be unable to connect to their Dedibox VPS in the Paris location due to a locked state.

  2. resolved Oct 08, 2026, 01:27 PM UTC

    This incident has been resolved.

Read the full incident report →