Monitoring - The situation should be back to normal
Nov 04, 2026 - 09:21 CET
Update - We are continuing to investigate this issue.
Nov 03, 2026 - 11:02 CET
Update - We are continuing to investigate this issue.
Nov 03, 2026 - 10:59 CET
Investigating - Issues with LB creation/configuration and auto-healing in PAR1 due to internal metadata API failure
Nov 03, 2026 - 10:54 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 04, 2026 - 08:00 CET
Update - We will be undergoing scheduled maintenance during this time.
Nov 4, 2026 08:00 - Nov 6, 2026 19:00 CET
Update - [Kapsule] - [All - region] - infrastructure migration
We will be undergoing scheduled maintenance during this time.

Nov 4, 2026 08:00 - Nov 6, 2026 19:00 CET
Update - We will be undergoing scheduled maintenance during this time.
Nov 4, 2026 08:00 - Nov 6, 2026 19:00 CET
Update - We will be undergoing scheduled maintenance during this time.
Nov 4, 2026 08:00 - Nov 6, 2026 19:00 CET
Scheduled - [Kapsule] - infrastructure migration

On Wednesday 4th to Friday 6th of November, from 8:00 AM CET to 7:00 PM CET, we will perform a mandatory upgrade on our infrastructure.

This upgrade aims to enhance internal resiliency. THIS IS NOT THE FORCE UPGRADE PROCESS.

This migration will cause apiserver restart one or more time.

We will keep you updated, and will inform you when the upgrade is finished.

We sincerely apologize for any inconvenience.

Nov 4, 2026 08:00 - Nov 6, 2026 19:00 CET
Monitoring - The situation should now be back to normal.
Nov 03, 2026 - 12:20 CET
Update - We are continuing to investigate this issue.
Nov 03, 2026 - 12:09 CET
Investigating - We are currently experiencing slow response time on Metadata API through VPC. This started at 09:00 UTC.
DNS through VPC may also experience slow response time.

Nov 03, 2026 - 12:08 CET
Monitoring - Some requests to the deepseek-v4-flash and deepseek-v4.1-flash models had experienced elevated timeouts.
The error rates are improving.
We're monitoring the situation.

Oct 26, 2026 - 18:34 CET
Update - [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 thank you for your patience.

Oct 26, 2026 - 17:55 CET
Update - [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.

Oct 22, 2026 - 08:20 CEST
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.

Oct 21, 2026 - 16:38 CEST
Identified - Due to a high volume of requests, it may be difficult to reach our teams by phone.
If needed, we invite you to contact us directly by submitting a ticket so that your request can be processed as quickly as possible.
Thank you for your understanding.

En raison d’un nombre élevé de demandes, il peut être difficile de joindre nos équipes par téléphone.
Au besoin, nous vous invitons à nous contacter directement par ticket afin que votre demande soit prise en charge dans les meilleurs délais.
Merci de votre compréhension.

Oct 26, 2026 - 09:56 CET
Investigating - Due to a high volume of requests, it may be difficult to reach our teams by phone.
If needed, we invite you to contact us directly by submitting a ticket so that your request can be processed as quickly as possible.
Thank you for your understanding.

En raison d’un nombre élevé de demandes, il peut être difficile de joindre nos équipes par téléphone.
Au besoin, nous vous invitons à nous contacter directement par ticket afin que votre demande soit prise en charge dans les meilleurs délais.
Merci de votre compréhension.

Oct 26, 2026 - 09:44 CET
Update - En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude.
Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais.
Nous vous remercions pour votre patience et votre compréhension.

Due to a high volume of requests, the processing of ongoing tickets may take longer than usual.
Our teams are fully mobilized to restore normal service and handle requests as quickly as possible.
Thank you for your patience and understanding.

Oct 26, 2026 - 09:55 CET
Identified - En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude.
Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais.
Nous vous remercions pour votre patience et votre compréhension.

Due to a high volume of requests, the processing of ongoing tickets may take longer than usual.
Our teams are fully mobilized to restore normal service and handle requests as quickly as possible.
Thank you for your patience and understanding.

Oct 26, 2026 - 09:54 CET
Investigating - En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude.
Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais.
Nous vous remercions pour votre patience et votre compréhension.

Due to a high volume of requests, the processing of ongoing tickets may take longer than usual.
Our teams are fully mobilized to restore normal service and handle requests as quickly as possible.
Thank you for your patience and understanding.

Oct 26, 2026 - 09:45 CET
Update - Scheduled maintenance is still in progress. Work is scheduled to be completed on the date indicated (15/11)
Oct 22, 2026 - 09:21 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 15, 2026 - 09:00 CEST
Update - We will be undergoing scheduled maintenance during this time.
Sep 15, 2026 09:00 - Nov 16, 2026 08:00 CET
Update - We will be undergoing scheduled maintenance during this time.
Sep 15, 2026 09:00 - Nov 16, 2026 08:00 CET
Update - We will be undergoing scheduled maintenance during this time.
Sep 15, 2026 09:00 - Nov 16, 2026 08:00 CET
Scheduled - As part of the work to replace the access control system, scheduled to take place from 15 September to 15 November, work will be carried out
in stages on certain access doors.
This work will include, in particular, the removal of the old readers and the installation and commissioning of the new readers.
During this transition period, and depending on the progress of the work, it may be necessary to temporarily use two access badges
for certain doors, in order to ensure continuity and the smooth operation of access.
Those affected will be informed in advance should this arrangement need to be put in place.
We thank you in advance for your understanding, patience and cooperation throughout the duration of this work.

Sep 15, 2026 09:00 - Nov 16, 2026 08:00 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 20, 2026 - 17:42 CEST
Investigating - Started Tuesday 20th October @ 5:04pm
The glm-5.3 model is consistently returning timeout errors on all requests. We are working at fixing the issue.

Oct 20, 2026 - 17:31 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 20, 2026 - 12:07 CEST
Investigating - We are currently experiencing degraded performance with it-mil APIs. Some requests may see elevated latency, intermittent errors, or timeouts. Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible.
Oct 20, 2026 - 11:23 CEST

About This Site

Welcome to the Scaleway Status website. Here, you can view the status of all Scaleway services across all products and availability zones (AZs).
You can check how subscribe, manage your email status updates and how to receive status notifications on Slack here: https://www.scaleway.com/en/docs/account/reference-content/scaleway-status-updates/

Elements - Products Degraded Performance
Account Operational
APIs Degraded Performance
Apple Silicon Operational
Audit Trail Operational
Billing Operational
Block Storage Operational
Cockpit Operational
Container Registry Operational
Data Warehouse Operational
Databases Operational
Developer Tools Operational
Domains Operational
Edge service Operational
Elastic Metal Operational
Elements Console Operational
Environmental Footprint Operational
File Storage Operational
Generative API Operational
IAM Operational
Instances Operational
IoT Hub Operational
Jobs Operational
Kafka Operational
Kubernetes Kapsule Under Maintenance
Load Balancer Degraded Performance
Managed Inference Operational
Messaging and Queuing Operational
Network Operational
Object Storage Operational
Observability Operational
Public Gateway Operational
Secret Manager Operational
Serverless Container Operational
Serverless Functions Operational
Serverless-Database Operational
Transactional Email Operational
VPC Degraded Performance
Web Hosting Operational
Website Operational
Clusters for Apache Spark™ Operational
Elements - AZ Under Maintenance
fr-par-1 Under Maintenance
fr-par-2 Operational
fr-par-3 Under Maintenance
nl-ams-1 Operational
nl-ams-2 Operational
nl-ams-3 Operational
pl-waw-1 Under Maintenance
pl-waw-2 Under Maintenance
pl-waw-3 Under Maintenance
it-mil-1 Under Maintenance
it-mil-2 Under Maintenance
it-mil-3 Under Maintenance
Dedibox - Products Under Maintenance
Dedibox Operational
Hosting Under Maintenance
SAN Operational
Dedirack Under Maintenance
Dedibackup Operational
Domains Operational
RPN Operational
Dedibox Console Operational
Dedibox VPS Operational
Dedibox - Datacenters Under Maintenance
DC1 Under Maintenance
DC2 Operational
DC3 Operational
DC4 Operational
DC5 Operational
AMS Operational
Miscellaneous Degraded Performance
Excellence Degraded Performance
BookMyName Operational
Saagie - Products Operational
Product-1-ACO Operational
Product-2-BOU Operational
Product-3-BV Operational
Product-6-SIPDEV Operational
Product-7-SIPINT Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Nov 6, 2026

No incidents reported today.

Nov 5, 2026

Completed - Maintenance has been stopped, due to issues encountered while we were rolling out changes. More details in the dedicated incident summary: https://status.scaleway.com/incidents/kpdnmppv771c.

We will resume the infrastructure upgrade process later, and will create a separate scheduled maintenance for it.

We apologize for any inconvenience.

Nov 5, 16:53 CET
Update - Maintenance did not go as planned and lead to connectivity issues. Refer to this dedicated status for more information: https://status.scaleway.com/incidents/kpdnmppv771c
Nov 5, 12:26 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 5, 09:01 CET
Scheduled - On 11/05, from 9:00 AM UTC, we will perform a mandatory upgrade on our nl-ams infrastructure.

This upgrade aims to fix a few issues, most notably a bug preventing functions/containers instances to downscale properly to zero even if no traffic is received. This will also include changes allowing us to improve overall performance, and prepare for the next features.

While we tried our best to reduce impacts to users, some of them are inevitable. While we rollout the upgrade, expected impacts are:

- Users' running functions/containers instances will restart, several times. As a result, requests could be buffered while new instances are started, causing "cold starts", even for functions/containers with min_scale set to 1. Functions/containers with no running instances won't be impacted.

- 5xx errors while calling functions/containers. As we restart system components to perform the upgrade, some in-flight requests (especially long-running ones) might be terminated before completion. Users might also notice flakiness (slow requests, timeouts), but client retries should be able to succeed.

We will keep you updated, and will inform you when the upgrade is finished.

We sincerely apologize for any inconvenience.

Oct 30, 11:03 CET
Resolved - Incident is resolved now.

Impacts for users were limited to nl-ams region, and Serverless Containers product:

- From 10:00 UTC to 11:05 UTC: users received HTTP 5xx errors while calling their containers
- From 10:00 UTC to 12:00 UTC: some containers were stuck in creating/updating
- From 09:20 UTC to 12:20 UTC: some containers with VPC support lost connectivity to resources in their PN

These were all unexpected impacts of the following maintenance: https://status.scaleway.com/incidents/f7lpf0j1c2sq. The upgrade was partially applied, since we stopped it to stabilize the situation. While the situation is stable now, some work will still need to be done to fully complete the maintenance in the future, but we will postpone it for now.

In more details: a faulty step during our maintenance caused 1) our gateways to misbehave and start returning HTTP 503 errors and 2) VPC attached containers to be detached from their PN. The situation quickly snowballed, as a lot of pressure was made on the infrastructure, causing other unrelated issues (e.g. containers stuck in creating/updating statuses).

Despite our care, and successful upgrades on other regions (e.g. https://status.scaleway.com/incidents/tf28nvnckksz), the issue arose there because of nl-ams region being more crowded. We will perform additional tests before continuing the maintenance.

We deeply apologize for the inconvenience caused.

Nov 5, 16:52 CET
Monitoring - VPC connectivity issues are now stabilized.

Unlike stated previously, only Serverless Containers product is impacted.

We are now monitoring the situation.

Thanks for your understanding.

Nov 5, 13:21 CET
Update - As of 12:00 UTC, containers shouldn't be stuck anymore in "creating" or "updating" status for an abnormal duration.

Some containers with VPC support might have lost connectivity to resources inside the Private Network. A redeployment of the container triggered by users could help solving the situation, but we are investigating.

Sorry again for any inconvenience.

Nov 5, 13:17 CET
Update - Connectivity has been back to normal since 11:06 UTC. We are continuing to monitor the situation.
We are still working on restoring create and update operations, which remain impacted.

Nov 5, 12:46 CET
Update - Serverless Container, Serverless Functions are impacted.
Nov 5, 12:24 CET
Identified - The scheduled maintenance https://status.scaleway.com/incidents/f7lpf0j1c2sq did not go as planned. Since 09:50 UTC, Serverless Containers services might have faced connectivity issues. Create and update operations were impacted as well.
Nov 5, 12:22 CET
Resolved - All emails have now been sent, and traffic is back to normal.
Nov 5, 16:33 CET
Monitoring - We have identified the issue and successfully restored outbound traffic. The problem was caused by a network configuration that failed to apply properly. We applied fix, which resolved the situation, and outgoing emails should start clearing and sending out gradually.
Nov 5, 15:08 CET
Identified - Some customers may experience emails getting stuck while processing or sending.
We are actively working to resolve the issue and sincerely apologize for the inconvenience caused.

Nov 5, 13:27 CET
Resolved - This incident has been resolved.
Nov 5, 15:35 CET
Monitoring - All new servers have been fixed.
We are still increasing data density in the servers and monitoring any latency spikes.

Nov 4, 17:40 CET
Update - We are continuing to work on a fix for this issue.
Nov 4, 17:38 CET
Update - The fix improved nvme behavior during the day and today we applied it on half of the concerned rack.
As data must be removed first to apply the fix, migrations operations are processing slowly to avoid worsening impact on latencies.
Migration operations will continue through the week-end.

Oct 30, 22:32 CET
Update - We applied a fix on one of the concerned servers and monitoring it, we will have more significant metrics tomorrow.
Oct 29, 17:52 CET
Identified - Since monday 26 october on the morning, we noticed increased periodic spike of latencies following the integration of a new rack in one of our cluster. Those spikes are more noticeable during the day and are linked to writes done on some of the new disks.
This issue also impact MRDB product.

We limited the impact and currently we are working on a fix. An update will be posted at the end of the day.

Oct 29, 12:01 CET
Completed - The scheduled maintenance has been completed.
Nov 5, 09:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 4, 09:00 CET
Scheduled - A technical modernization process is currently underway on selected infrastructure in the PAR2 availability zone.
- Impacted servers: EM-I215E-NVME dedicated servers with tag 'migration_required'.
- Action Required: Impacted customers have received a dedicated email to perform a complimentary migration to a new server before November 4, 2026.
- Unmigrated servers will be proactively powered off on November 4, 2026, to allow completion of the maintenance work.

Our support team remains at your disposal to assist you throughout this migration process.

Oct 22, 17:23 CEST

Nov 4, 2026

Resolved - This incident has been resolved.
Nov 4, 16:15 CET
Investigating - Some customers may experience errors while pushing traces on pl-waw.
Nov 4, 13:37 CET

Nov 3, 2026

Resolved - This incident has been resolved.
Nov 3, 15:13 CET
Monitoring - The issue was identified on LB's side; the problem is now resolved.

We're monitoring for the time being but don't expect any reoccurrence.

Nov 3, 11:06 CET
Investigating - We are investigating reports that some serverless containers in the fr-par region may be unreachable. The issue appears to be caused by a load balancer being down, affecting a subset of the serverless containers on fr-par.
Nov 3, 11:03 CET
Completed - The maintenance is now over.

The infrastructure upgrade went well, and has been done between 09:00 UTC and 10:20 UTC. During this period, users might have encountered a few disturbances, listed in the initial message.

Sorry again for any inconvenience, thanks for your understanding.

Nov 3, 13:07 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 3, 09:00 CET
Scheduled - On 11/03, from 9:00 AM UTC, we will perform a mandatory upgrade on our pl-waw infrastructure.

This upgrade aims to fix a few issues, most notably a bug preventing functions/containers instances to downscale properly to zero even if no traffic is received. This will also include changes allowing us to improve overall performance, and prepare for the next features.

While we tried our best to reduce impacts to users, some of them are inevitable. While we rollout the upgrade, expected impacts are:

- Users' running functions/containers instances will restart, several times. As a result, requests could be buffered while new instances are started, causing "cold starts", even for functions/containers with min_scale set to 1. Functions/containers with no running instances won't be impacted.

- 5xx errors while calling functions/containers. As we restart system components to perform the upgrade, some in-flight requests (especially long-running ones) might be terminated before completion. Users might also notice flakiness (slow requests, timeouts), but client retries should be able to succeed.

We will keep you updated, and will inform you when the upgrade is finished.

We sincerely apologize for any inconvenience.

Oct 26, 11:57 CET
Resolved - This incident has been resolved.
Nov 3, 11:58 CET
Investigating - Both switches in the rack DC3/S46/B09-10 went offline.
Nov 3, 09:35 CET
Resolved - The situation went back to normal around 7:30 Paris time
Nov 3, 08:54 CET
Investigating - November consumptions are not up to date in billing console and billing APIs. We are working at resolving this issue.
Nov 2, 15:42 CET

Nov 2, 2026

Resolved - This incident has been resolved.
Nov 2, 14:59 CET
Identified - Following this incident : https://status.scaleway.com/incidents/4v0ls9gl5f1k
To avoid further issues, Serverless SQL DB will not run backups on Friday night or Saturday night. We will start running backups on Monday morning.

Oct 30, 11:15 CET
Resolved - Resolved at 2026 Nov 2 12:22:44 UTC

No root cause found (nothing in the logs and console unresponsive).
Fixed with a cold reboot

Nov 2, 13:46 CET
Investigating - RPN service is unavailable since 2026 Nov 2 09:47:04 UTC
Rack impacted : DC5/S9/C52

Nov 2, 11:28 CET
Resolved - 01/11/2026 - 21:00 UTC+1 - Service started to be degradated
02/11/2026 - 2:00 UTC+1 - Service was unavailable
02/11/2026 - 9:00 UTC+1 - A fix has been implemented, service is available

Nov 2, 09:19 CET

Nov 1, 2026

Resolved - 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.”
Nov 1, 22:17 CET

Oct 31, 2026

No incidents reported.

Oct 30, 2026

Resolved - This incident has been resolved.
Oct 30, 10:53 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 29, 11:00 CET
Update - We are continuing to work on a fix for this issue.
Oct 29, 10:31 CET
Identified - Serverless SQL is experiencing performance degradation, serverless SQL databases are repeatedly restarting, and our team is actively investigating the issue.
Oct 29, 09:59 CET

Oct 29, 2026

Resolved - This incident has been resolved.
Oct 29, 15:13 CET
Investigating - Customers on pf-13 may currently experience database connection issues. As a result, CMS applications like WordPress might be unavailable and display database connection errors. Our team is now investigating.
Oct 28, 19:39 CET
Resolved - 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.

Oct 29, 14:28 CET
Resolved - This incident has been resolved.
Oct 29, 11:49 CET
Investigating - [10:06] Requests on model had experienced elevated timeouts.
[10:15] Model has been unavailable
[10:50] Fix has been applied

Oct 27, 12:03 CET
Resolved - The IP address 51.159.124.109 has been blacklisted by Spamhaus.

It is possible that some emails may still be rejected if this listing is cached.

The incident for this IP address lasted from:
Date Listed: October 28, 2026, 6:46:49 PM
Date Removed: October 28, 2026, 8:54:39 PM

Oct 29, 08:43 CET
Investigating - The IP address 51.159.124.109 has been blacklisted by Spamhaus.
Oct 29, 08:30 CET

Oct 28, 2026

Completed - The scheduled maintenance has been completed.
Oct 28, 19:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 28, 07:00 CET
Scheduled - On Wednesday 28th of October, from 7:00 AM UTC to 7:00 PM UTC, we will perform a mandatory upgrade on our it-mil infrastructure.

This upgrade aims to improve etcd performance issues on it-mil.

This migration will cause some downtime on the apiserver and controllers/operators:

- APIServers will be down for a few minutes
- Controllers and operators will be restarted in loops until migration is complete
- Kubelet will be restarted too

We will keep you updated, and will inform you when the upgrade is finished.

We sincerely apologize for any inconvenience.

Oct 27, 10:37 CET
Resolved - This incident has been resolved.
Oct 28, 18:07 CET
Investigating - 2026-10-26 11:40:37 GMT+1: a new image was released for Kapsule nodes, unfortunately the release seems to be only partial and some regions might not have the right image id.
This may cause nodes to be unable to spawn.

Oct 26, 13:18 CET
Completed - The scheduled maintenance has been completed.
Oct 28, 18:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 27, 09:00 CET
Scheduled - The Kapsule node agent (k8s-agent), which manages the Kubernetes components installed on nodes, will be upgraded in-place on Kapsule nodes.

Impact: none expected on workloads.
- Only the agent itself is replaced and restarted.
- No Kubernetes component (kubelet, containerd, runc, CNI plugins) will be restarted, reinstalled or upgraded.
- Nodes will not be drained, cordoned or rebooted, and pods will keep running.

Kosmos (external) nodes are not affected.

Oct 26, 09:49 CET
Completed - The scheduled maintenance has been completed.
Oct 28, 12:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 28, 10:00 CET
Scheduled - On Wednesday October 28th, 2026, from 10:00 AM to 12:00 AM (CET), we would like to inform you that a scheduled operation will take place on Kafka in it-mil.
Reason for maintenance: Migration of an infrastructure component
During the maintenance window your Kafka client might be disconnected from the server, it will automatically reconnect to another server.

The products will remain available, but there might be a disruption of the service for some minutes

We will keep you updated, and will inform you when the upgrade is finished.

We sincerely apologize for any inconvenience.

Oct 27, 16:25 CET

Oct 27, 2026

Resolved - This incident has been resolved.
Oct 27, 17:33 CET
Update - We are continuing to investigate this issue.
Oct 27, 17:33 CET
Investigating - Since 14:51 UTC, new RDB instance can't be provisioning in AMS
Oct 27, 17:32 CET
Resolved - This incident has been resolved.
Oct 27, 15:27 CET
Investigating - [12:00]
Serverless Container creation is currently unavailable in it-mil due to communication issues within the Kubernetes cluster.

Oct 27, 15:23 CET
Resolved - This incident has been resolved.
Oct 27, 11:36 CET
Identified - On 2026-10-21, a critical PHP RCE (CVE-2026-109618/109619, CVSS 9.2) forced an emergency migration of the BookMyName services. The migration introduced PHP compatibility regressions in legacy code, impacting customers since 2026-10-21.
Oct 23, 16:24 CEST

Oct 26, 2026

Resolved - Some requests to the deepseek-v4.1-flash model had experienced elevated timeouts.
The situation has been resolved.

Oct 26, 09:48 CET
Resolved - This incident has been resolved.
Oct 26, 09:46 CET
Identified - En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude.
Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais.
Nous vous remercions pour votre patience et votre compréhension.

Due to a high volume of requests, the processing of ongoing tickets may take longer than usual.
Our teams are fully mobilized to restore normal service and handle requests as quickly as possible.
Thank you for your patience and understanding.

Oct 8, 18:35 CEST
Resolved - This incident has been resolved.
Oct 26, 09:44 CET
Identified - Due to a high volume of requests, it may be difficult to reach our teams by phone.
If needed, we invite you to contact us directly by submitting a ticket so that your request can be processed as quickly as possible.
Thank you for your understanding.

En raison d’un nombre élevé de demandes, il peut être difficile de joindre nos équipes par téléphone.
Au besoin, nous vous invitons à nous contacter directement par ticket afin que votre demande soit prise en charge dans les meilleurs délais.
Merci de votre compréhension.

Oct 8, 18:27 CEST

Oct 25, 2026

No incidents reported.

Oct 24, 2026

No incidents reported.

Oct 23, 2026

Resolved - This incident has been resolved.
Oct 23, 11:11 CEST
Investigating - Due to an abnormal charge, some Scaleway product logs might have been ingested with delay and some might have been dropped

We observe some drop on Serverless logs

This issue is now resolved

Oct 23, 11:06 CEST
Resolved - This incident has been resolved.
Oct 23, 09:22 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 22, 17:26 CEST
Investigating - RPN service unreachable for this rack since 2026/10/22 06:45 UTC
Oct 22, 11:36 CEST