Status impact color legend
- Black impact: None
- Yellow impact: Minor
- Red impact: Major
- Blue impact: Maintenance
Monitoring - Nos équipes ont identifié et isolé la cause de l'incident affectant les informations de contact de vos noms de domaine.
Le service sera pleinement rétabli dans la soirée. Vous pourrez alors administrer vos noms de domaine normalement. Veuillez noter toutefois que certaines fonctionnalités secondaires resteront temporairement indisponibles.
Compte tenu du rétablissement effectif du service ce jour, les renouvellements automatiques seront assurés sans interruption. Par conséquent, et contrairement à ce qui a pu être communiqué précédemment, nous ne procéderons pas au renouvellement gracieux des domaines arrivant à échéance ce 5 mai 2026. Ces derniers seront traités selon vos modalités de facturation habituelles.
—--
Our teams have identified and resolved the cause of the incident affecting your domain name contact details.
The service will be fully restored this evening. You will then be able to manage your domain names as normal. Please note, however, that some secondary features will remain temporarily unavailable.
Given that the service has been fully restored today, automatic renewals will continue without interruption. Consequently, and contrary to what may have been previously communicated, we will not be offering a complimentary renewal for domains expiring on 5 May 2026. These will be processed in accordance with your usual billing terms.
May 05, 2026 - 22:00 CEST
Le service sera pleinement rétabli dans la soirée. Vous pourrez alors administrer vos noms de domaine normalement. Veuillez noter toutefois que certaines fonctionnalités secondaires resteront temporairement indisponibles.
Compte tenu du rétablissement effectif du service ce jour, les renouvellements automatiques seront assurés sans interruption. Par conséquent, et contrairement à ce qui a pu être communiqué précédemment, nous ne procéderons pas au renouvellement gracieux des domaines arrivant à échéance ce 5 mai 2026. Ces derniers seront traités selon vos modalités de facturation habituelles.
—--
Our teams have identified and resolved the cause of the incident affecting your domain name contact details.
The service will be fully restored this evening. You will then be able to manage your domain names as normal. Please note, however, that some secondary features will remain temporarily unavailable.
Given that the service has been fully restored today, automatic renewals will continue without interruption. Consequently, and contrary to what may have been previously communicated, we will not be offering a complimentary renewal for domains expiring on 5 May 2026. These will be processed in accordance with your usual billing terms.
May 05, 2026 - 22:00 CEST
Update - À ce stade, nous confirmons que les noms de domaine enregistrés auprès de Bookmyname ne présentent aucun risque identifié.
Les modifications intervenues sur les informations de contact associées ont été entièrement rétablies dans leur configuration initiale.
À ce stade de nos investigations, nous ne sommes pas en mesure de vous informer d’une date de reprise du service.
Compte tenu des délais nécessaires à l’analyse, et à titre exceptionnel et gracieux, nous procéderons au renouvellement des noms de domaine arrivant à échéance dans un délai de 72 heures à compter du mardi 5 mai 2026 à 08h00, afin de prévenir tout incident lié à leur renouvellement.
—--
At this stage, we confirm that the domain names registered with Bookmyname present no identified risk.
The changes made to the associated contact information have been fully restored to their original configuration.
At the current stage of our investigations, we are not in a position to provide a service restoration date.
Given the time required for the analysis, and on an exceptional and goodwill basis, we will proceed with the renewal of any domain names due to expire within 72 hours from Tuesday, May 5, 2026 at 08:00, in order to prevent any incident related to their renewal.
May 05, 2026 - 17:31 CEST
Les modifications intervenues sur les informations de contact associées ont été entièrement rétablies dans leur configuration initiale.
À ce stade de nos investigations, nous ne sommes pas en mesure de vous informer d’une date de reprise du service.
Compte tenu des délais nécessaires à l’analyse, et à titre exceptionnel et gracieux, nous procéderons au renouvellement des noms de domaine arrivant à échéance dans un délai de 72 heures à compter du mardi 5 mai 2026 à 08h00, afin de prévenir tout incident lié à leur renouvellement.
—--
At this stage, we confirm that the domain names registered with Bookmyname present no identified risk.
The changes made to the associated contact information have been fully restored to their original configuration.
At the current stage of our investigations, we are not in a position to provide a service restoration date.
Given the time required for the analysis, and on an exceptional and goodwill basis, we will proceed with the renewal of any domain names due to expire within 72 hours from Tuesday, May 5, 2026 at 08:00, in order to prevent any incident related to their renewal.
May 05, 2026 - 17:31 CEST
Update - At 08:55 CEST on May 5th, we detected an unusual activity on the BookMyName Information System.
Customers may have seen a modification of their contact information related to their domain names.
Due to that we have decided to shutdown all public access to BookMyname the time for us to perform the investigation.
From our first round of investigation we have not seen any zone modification or domain transfer out.
We will keep you updated on any progress we will make on the investigation.
—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-
Le 5 mai à 08h55 (CEST), nous avons détecté une activité inhabituelle sur le système d’information de BookMyName.
Certains clients ont pu constater une modification de leurs informations de contact associées à leurs noms de domaine.
En conséquence, nous avons décidé de suspendre l’ensemble des accès publics à BookMyName le temps de mener les investigations nécessaires.
À ce stade de nos analyses, aucune modification des zones DNS ni aucun transfert de domaine sortant n’ont été constatés.
Nous vous tiendrons informés de toute avancée significative dans le cadre de cette enquête.
May 05, 2026 - 13:07 CEST
Customers may have seen a modification of their contact information related to their domain names.
Due to that we have decided to shutdown all public access to BookMyname the time for us to perform the investigation.
From our first round of investigation we have not seen any zone modification or domain transfer out.
We will keep you updated on any progress we will make on the investigation.
—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-
Le 5 mai à 08h55 (CEST), nous avons détecté une activité inhabituelle sur le système d’information de BookMyName.
Certains clients ont pu constater une modification de leurs informations de contact associées à leurs noms de domaine.
En conséquence, nous avons décidé de suspendre l’ensemble des accès publics à BookMyName le temps de mener les investigations nécessaires.
À ce stade de nos analyses, aucune modification des zones DNS ni aucun transfert de domaine sortant n’ont été constatés.
Nous vous tiendrons informés de toute avancée significative dans le cadre de cette enquête.
May 05, 2026 - 13:07 CEST
Update - We are continuing to investigate this issue.
May 05, 2026 - 11:11 CEST
May 05, 2026 - 11:11 CEST
Investigating - All BookMyName services are unavailable, and we are currently investigating the root cause. Domain management on Scaleway and Dedibox are also impacted.
May 05, 2026 - 08:55 CEST
May 05, 2026 - 08:55 CEST
Identified - Customers may experience failing workflows on Redis such as provisioning new instances
May 05, 2026 - 18:53 CEST
May 05, 2026 - 18:53 CEST
Update - Data Warehouse experiencing issues creating new deployments
May 05, 2026 - 17:01 CEST
May 05, 2026 - 17:01 CEST
Update - The following services are impacted by this incident :
- Kapsule Control Plane API for new clusters and some existing cluster unreachable
- LBs are experiencing configuration latencies, which impacts Kapsule node scaling
May 05, 2026 - 15:27 CEST
- Kapsule Control Plane API for new clusters and some existing cluster unreachable
- LBs are experiencing configuration latencies, which impacts Kapsule node scaling
May 05, 2026 - 15:27 CEST
Investigating - We are currently observing connectivity issues with Load Balancers caused by a partial outage on an internal dependency in the fr-par-1 region.
May 05, 2026 - 14:23 CEST
May 05, 2026 - 14:23 CEST
Investigating - Customers may experience unavailability on Serverless SQL DB in the fr-par region.
May 05, 2026 - 14:58 CEST
May 05, 2026 - 14:58 CEST
Investigating - Due to ongoing incident on BookMyName, our migration flow is failing due to nameservers unavailability.
We will relaunch the migration once the BMN incident is resolved.
May 05, 2026 - 12:45 CEST
We will relaunch the migration once the BMN incident is resolved.
May 05, 2026 - 12:45 CEST
[WEBHOSTING] SMTP/51.159.208.135 blacklisted on Microsoft/Outlook from classic webhosting service
Subscribe
Identified - Our service is currently experiencing disruption due to blacklisting by Microsoft.
We are actively working with Microsoft to resolve this issue as soon as possible.
Nov 24, 2025 - 19:34 CET
We are actively working with Microsoft to resolve this issue as soon as possible.
Nov 24, 2025 - 19:34 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 05, 2026 - 10:00 CEST
May 05, 2026 - 10:00 CEST
Scheduled - From May 5th to May 6th (between 10:00 AM and 7:00 PM CEST), we will perform a mandatory operation in the fr-par region to release VPC routing.
Over the course of these two days, changes will be applied to all Serverless Functions namespaces in the fr-par region.
While this operation is seamless most of the time, users may observe the following behaviors:
- Namespaces will pass temporarily in "unknown" status. This may take up to 15 minutes, depending on the number of resources inside the namespace.
- Function instances will be created. This is mandatory to ensure the functions are working properly. If a function fails to start, the "status" field will change to "error", and the "error_message" field will show the error, so users can fix it. During that process, users could see multiple instances of their function running, even if it's configured with max_scale = 1, and even if there is no incoming traffic. The function will downscale as soon as the operation is over.
- Long running requests made during this operation may fail, as we roll out function instances.
- Crons might be triggered multiple times during the operation. Crons with frequent schedules (such as every minute) might be more impacted.
Please note that during this process, unless the functions cannot start because of an applicative error, the functions will always be reachable.
Thank you for your understanding, and we apologize for any inconvenience this may cause.
May 5, 2026 10:00 - May 6, 2026 19:00 CEST
Over the course of these two days, changes will be applied to all Serverless Functions namespaces in the fr-par region.
While this operation is seamless most of the time, users may observe the following behaviors:
- Namespaces will pass temporarily in "unknown" status. This may take up to 15 minutes, depending on the number of resources inside the namespace.
- Function instances will be created. This is mandatory to ensure the functions are working properly. If a function fails to start, the "status" field will change to "error", and the "error_message" field will show the error, so users can fix it. During that process, users could see multiple instances of their function running, even if it's configured with max_scale = 1, and even if there is no incoming traffic. The function will downscale as soon as the operation is over.
- Long running requests made during this operation may fail, as we roll out function instances.
- Crons might be triggered multiple times during the operation. Crons with frequent schedules (such as every minute) might be more impacted.
Please note that during this process, unless the functions cannot start because of an applicative error, the functions will always be reachable.
Thank you for your understanding, and we apologize for any inconvenience this may cause.
May 5, 2026 10:00 - May 6, 2026 19:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 05, 2026 - 09:00 CEST
May 05, 2026 - 09:00 CEST
Scheduled - The infrastructure hosting Kapsule control planes in the fr-par region is scheduled for an upgrade. During this maintenance window, control planes will be restarted.
Data plane workloads (nodes and pods) will not be affected, but the Kubernetes API server will be briefly unavailable during the restart.
May 5, 2026 09:00 - May 6, 2026 18:00 CEST
Data plane workloads (nodes and pods) will not be affected, but the Kubernetes API server will be briefly unavailable during the restart.
May 5, 2026 09:00 - May 6, 2026 18:00 CEST
Identified - Customers may experience issues resulting using our APIs in the it-mil-1 region.
May 04, 2026 - 14:54 CEST
May 04, 2026 - 14:54 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
May 03, 2026 - 15:41 CEST
May 03, 2026 - 15:41 CEST
Update - The engineers on our Edge Services team are still investigating the situation.
May 03, 2026 - 14:41 CEST
May 03, 2026 - 14:41 CEST
Investigating - Our Edge Services are currently unavailable; our engineers are already investigating the issue.
We will update this status as soon as we have more information.
May 03, 2026 - 13:21 CEST
We will update this status as soon as we have more information.
May 03, 2026 - 13:21 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 30, 2026 - 18:03 CEST
Apr 30, 2026 - 18:03 CEST
Identified - Customers may experience issues with Block Storage snapshot operations in the FR-PAR-1 region. Our engineering team has identified the root cause and is working on a solution to restore normal operations. We will provide further updates as soon as the issue is resolved. Thank you for your patience.
Apr 30, 2026 - 17:46 CEST
Apr 30, 2026 - 17:46 CEST
Investigating - Some RDB instances in the FR‑PAR‑1 region are currently stuck in the "snapshotting" state. Our engineering team is actively working to release the affected instances and restore normal snapshot operations.
We will provide further updates as soon as the issue is resolved. Thank you for your patience
Apr 30, 2026 - 17:15 CEST
We will provide further updates as soon as the issue is resolved. Thank you for your patience
Apr 30, 2026 - 17:15 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 30, 2026 - 11:48 CEST
Apr 30, 2026 - 11:48 CEST
Update - Customers may experience failures when accessing Object Storage in the Milan region due to an issue during an upgrade. The team is rolbacking this change.
The issue started at 09:05 UTC and ended at 09:41 UTC
Apr 30, 2026 - 11:48 CEST
The issue started at 09:05 UTC and ended at 09:41 UTC
Apr 30, 2026 - 11:48 CEST
Identified - Customers may experience failures when accessing Object Storage in the Milan region due to an issue during an upgrade.
The team is rollbacking this change.
Apr 30, 2026 - 11:32 CEST
The team is rollbacking this change.
Apr 30, 2026 - 11:32 CEST
Monitoring - Dedibox customers in rack DC5/S1/C57 may experienced network connectivity issues on the rpn network due to a switch reboot.
Apr 28, 2026 - 14:10 CEST
Apr 28, 2026 - 14:10 CEST
Identified - Ranged GetObject requests on SSE-(C/ONE) objects might fail, no impact on user data, a fix has been found and will be deployed shortly.
Mar 24, 2026 - 15:27 CET
Mar 24, 2026 - 15:27 CET
Investigating - We are currently investigating an issue affecting some card operations processed through Stripe. This may impact both the addition of new cards and, potentially, some payments requiring Stripe authentication.
Apr 20, 2026 - 09:43 CEST
Apr 20, 2026 - 09:43 CEST
Update - We are still unable to send SMS to US numbers.
The issue is due to A2P 10DLC regulations, which require registration and approval.
We have submitted the necessary requests to our providers, the approval process takes a minimum of 3 weeks.
We will provide updates as soon as we have more information.
Jul 21, 2025 - 10:30 CEST
The issue is due to A2P 10DLC regulations, which require registration and approval.
We have submitted the necessary requests to our providers, the approval process takes a minimum of 3 weeks.
We will provide updates as soon as we have more information.
Jul 21, 2025 - 10:30 CEST
Identified - The issue has been identified and a fix is being implemented.
Jul 17, 2025 - 15:14 CEST
Jul 17, 2025 - 15:14 CEST
Investigating - We are currently experiencing an issue where messages containing a phone number in the USA are not being properly routed by our SMS provider.
A ticket has been opened on their side.
We are actively monitoring the situation and will share updates as soon as available.
Jul 16, 2025 - 12:15 CEST
A ticket has been opened on their side.
We are actively monitoring the situation and will share updates as soon as available.
Jul 16, 2025 - 12:15 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
Major Outage
Account
Operational
APIs
Operational
Apple Silicon
Operational
Billing
Operational
Block Storage
Operational
Container Registry
Operational
Data Warehouse
Operational
Databases
Operational
Developer Tools
Operational
Domains
Partial Outage
Edge service
Major Outage
Elastic Metal
Operational
Elements Console
Operational
Environmental Footprint
Operational
Generative API
Operational
IAM
Operational
Instances
Operational
IoT Hub
Operational
Jobs
Operational
Kafka
Operational
Kubernetes Kapsule
Under Maintenance
Load Balancer
Partial Outage
Managed Inference
Operational
Messaging and Queuing
Operational
Network
Operational
Object Storage
Operational
Observability
Operational
Private Network
Operational
Public Gateway
Operational
Secret Manager
Operational
Serverless Container
Operational
Serverless Functions
Operational
Serverless-Database
Degraded Performance
Transactional Email
Operational
Web Hosting
Operational
Website
Operational
Elements - AZ
Operational
fr-par-1
Operational
fr-par-2
Operational
fr-par-3
Operational
nl-ams-1
Operational
nl-ams-2
Operational
nl-ams-3
Operational
pl-waw-1
Operational
pl-waw-2
Operational
pl-waw-3
Operational
Dedibox - Products
Partial Outage
Dedibox
Operational
Hosting
Partial Outage
SAN
Operational
Dedirack
Operational
Dedibackup
Operational
Domains
Partial Outage
RPN
Operational
Dedibox Console
Operational
Dedibox VPS
Operational
Dedibox - Datacenters
Degraded Performance
DC1
Operational
DC2
Operational
DC3
Operational
DC4
Operational
DC5
Degraded Performance
AMS
Operational
Miscellaneous
Major Outage
Excellence
Operational
BookMyName
Major Outage
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