Scaleway Outage History
Scaleway degraded · 4 active incidents · 2 long-running issues View live status →Pingoru has recorded 363 incidents for Scaleway: 362 in the last 12 months and 133 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 36 | 646 of 720 (90%) |
| May 2026 | 45 | 723 of 744 (97%) |
| June 2026 | 60 | 575 of 720 (80%) |
| July 2026 | 65 | 654 of 744 (88%) |
| August 2026 | 34 | 572 of 744 (77%) |
| September 2026 | 47 | 720 of 720 (100%) |
| October 2026 | 44 | 593 of 593 (100%) |
Incidents, newest first
Minor May 22, 2026 Kafka cluster not reachable - Connection to Kafka clusters fails. 2h 28m Kafka
Started May 22, 2026, 09:16 AM UTC· resolved May 22, 2026, 11:45 AM UTC
- investigating May 22, 2026, 09:16 AM UTC
We are currently investigating on that incident.
- investigating May 22, 2026, 09:17 AM UTC
We are continuing to investigate this issue.
- resolved May 22, 2026, 11:45 AM UTC
Following an infrastructure update, the Kafka clusters were no longer reachable via the private network. The issue has been resolved, and the services are operational again.
Major May 19, 2026 [API Gateway] - [world] APIs instabilities 19h 40m APIs
Started May 19, 2026, 12:34 PM UTC· resolved May 20, 2026, 08:15 AM UTC
- investigating May 19, 2026, 12:34 PM UTC
Customers may experience Network issues contacting our APIs. We are currently investigating this issue.
- resolved May 20, 2026, 08:15 AM UTC
This incident has been resolved.
Minor May 19, 2026 [Apple Silicon] - [fr-par-1] Increased delivery & installation time for Apple Silicon machines 2h 41m Apple Silicon
Started May 19, 2026, 09:33 AM UTC· resolved May 19, 2026, 12:14 PM UTC
- investigating May 19, 2026, 09:33 AM UTC
Customers may experience issues caused by a PostgreSQL LISTEN/NOTIFY bug in fr-par-1. Configuration/installation workflows on Mac-Mini servers are currently unable to complete. We are working to restablish the service as fast as possible.
- resolved May 19, 2026, 12:14 PM UTC
This incident has been resolved.
Critical May 19, 2026 [Identity and Access Management] - [world] API unavailable 3h 14m APIs
Started May 19, 2026, 09:07 AM UTC· resolved May 19, 2026, 12:22 PM UTC
- investigating May 19, 2026, 09:07 AM UTC
Customers may experience API errors when interacting with Identity and Access Management due to an internal dependency issue. Impact from 10.55 am to 11.01 am
- monitoring May 19, 2026, 09:19 AM UTC
From 10:55AM CET to 11:01AM CET, an incident occured on the IAM service. Impacts include: -All management actions on Groups, Policies, Applications, API keys ans Users were impossible -Some console users may have been automatically logged out -Login on console was unavailable -Some products with direct dependencies on IAM were partly unavailable on some limited control plane endpoints, mostly on Create endpoints: SSH keys, Kubernetes, MongoDB, Serverless products, Block Storage, Edge Services, VPC Secret Manager. A fix has been deployed on 11:01 CET, immediately fixing root cause and all impacts. Our teams are monitoring the issue.
- resolved May 19, 2026, 12:22 PM UTC
This incident has been resolved.
Notice May 18, 2026 [DNSE] - API slow –
Started May 18, 2026, 01:56 PM UTC· resolved May 18, 2026, 01:56 PM UTC
- resolved May 18, 2026, 01:56 PM UTC
The incident affected the API on our DNS Management for Elements. We had an API answer time issue between 14:43 and 14:51.
Minor May 18, 2026 Generative API instabilities 2h 26m Generative API
Started May 18, 2026, 01:07 PM UTC· resolved May 18, 2026, 03:33 PM UTC
- investigating May 18, 2026, 01:07 PM UTC
Customers may encounter 403 or 500 errors when querying the service. The root cause has been identified, and we're working on a fix.
- resolved May 18, 2026, 03:33 PM UTC
This incident has been resolved.
Minor May 15, 2026 [KUBE] - [it-mil] - creating/upgrade cluster issue 3d 2h Kubernetes Kapsule
Started May 15, 2026, 08:41 AM UTC· resolved May 18, 2026, 11:09 AM UTC
- investigating May 15, 2026, 08:41 AM UTC
Due to an internal dependency, all upgrades and new cluster creations on IT-Mil are currently blocked. Our team is actively working on a solution.
- resolved May 18, 2026, 11:09 AM UTC
This incident has been resolved.
Minor May 13, 2026 [Instance Orchestration] - [fr-par-2] No public IPv4 available 2h 30m fr-par-2, APIs, Billing, Block Storage and 5 more
Started May 13, 2026, 07:57 AM UTC· resolved May 13, 2026, 10:28 AM UTC
- investigating May 13, 2026, 07:57 AM UTC
We are currently unable to assigne IPv4 adresses in the Paris (fr-par-2) region. This may affect the creation of new instances requiring a public IPv4 address
- resolved May 13, 2026, 10:28 AM UTC
This incident has been resolved.
Minor May 11, 2026 [WebHosting Elements] - [fr-par] Platform connectivity issues 18m Hosting
Started May 11, 2026, 03:19 PM UTC· resolved May 11, 2026, 03:38 PM UTC
- investigating May 11, 2026, 03:19 PM UTC
Customers may experience connectivity issues on the WebHosting platform pf-1005. Our teams are working to resolve the issue.
- resolved May 11, 2026, 03:38 PM UTC
This incident has been resolved.
Minor May 11, 2026 [OBJS] - [nl-AMS] Object Storage availability issues on AMS 18d 4h nl-ams-1, nl-ams-2, nl-ams-3, Object Storage
Started May 11, 2026, 11:45 AM UTC· resolved May 29, 2026, 04:12 PM UTC
- investigating May 11, 2026, 11:45 AM UTC
Due to 2 servers of the same Object Storage cluster being down in 2 different AZ, access to data stored on that cluster can return 500 errors. Our team is on it.
- monitoring May 11, 2026, 12:39 PM UTC
The issue on the second server have been fixed. The major impact started from 10h37 UTC to 11h53 UTC with roughly 1% of AMS requests resulting in errors. The team is now monitoring the situation.
- resolved May 29, 2026, 04:12 PM UTC
This incident has been resolved.
Major May 6, 2026 [Cockpit] - [nl-ams/pl-waw] Elevated error rates on metrics and logs 3h 42m Observability
Started May 06, 2026, 09:06 AM UTC· resolved May 06, 2026, 12:49 PM UTC
- investigating May 06, 2026, 09:06 AM UTC
Customers may experience elevated error rates on metrics and logs in Cockpit on the nl-ams and pl-waw regions.
- resolved May 06, 2026, 12:49 PM UTC
Customers may have experienced elevated error rates on metrics and logs in Cockpit on the nl-ams and pl-waw regions. The issue has been resolved and service is back to normal.
Minor May 6, 2026 [DRPN] - [DC5 room 1 rack D13 blocks K and L] - RPN switch down 1h 10m RPN
Started May 06, 2026, 07:59 AM UTC· resolved May 06, 2026, 09:09 AM UTC
- investigating May 06, 2026, 07:59 AM UTC
Customers may experience RPN connectivity issues with Dedibox servers in DC5 room 1 rack D13 block K and L due to an unreachable RPN switch. Public connectivity is not affected.
Minor May 6, 2026 [Dedibox RPN] - [DC5 room 1 rack D13 block F] - RPN switch down 1h 17m Dedibox, RPN
Started May 06, 2026, 07:44 AM UTC· resolved May 06, 2026, 09:01 AM UTC
- investigating May 06, 2026, 07:44 AM UTC
Customers may experience RPN connectivity issues with Dedibox servers in DC5 room 1 rack D13 block K and L due to an unreachable RPN switch. Public connectivity is not affected.
- resolved May 06, 2026, 09:01 AM UTC
Customers may have experienced RPN connectivity issues with Dedibox servers in DC5 room 1 rack D13 blocks K and L due to an unreachable RPN switch. Public connectivity was not affected.
Notice May 5, 2026 [DNS Management for Elements] - Partial outage on DNS record management – Databases, Load Balancer, Object Storage, Transactional Email and 2 more
Started May 05, 2026, 08:30 PM UTC· resolved May 05, 2026, 08:30 PM UTC
- resolved May 06, 2026, 07:01 AM UTC
Customers may have experienced errors when managing DNS records due to a partial outage on the DNS Management for Elements service. It happened around 22h30 on 2026/05/05
Minor May 5, 2026 [Redis] - [fr-par, nl-ams, pl-war] Failing provisioning and workflows 21d 19h Databases
Started May 05, 2026, 04:53 PM UTC· resolved May 27, 2026, 12:28 PM UTC
- identified May 05, 2026, 04:53 PM UTC
Customers may experience failing workflows on Redis such as provisioning new instances
- resolved May 27, 2026, 12:28 PM UTC
This incident has been resolved.
Minor May 5, 2026 [DDBX] - [world] - Order/renewal validation is broken 54m Dedibox Console
Started May 05, 2026, 03:55 PM UTC· resolved May 05, 2026, 04:50 PM UTC
- investigating May 05, 2026, 03:55 PM UTC
Customers may experience issues when validating VPS, webhostings and domains orders. Issue is currently being investigated. Updates will be shared as soon as we have additional details.
- resolved May 05, 2026, 04:50 PM UTC
This incident has been resolved.
Major May 5, 2026 [Managed Inference] - [fr-par] Dedicated Deployments unavailability 4h 37m Managed Inference
Started May 05, 2026, 01:39 PM UTC· resolved May 05, 2026, 06:17 PM UTC
- identified May 05, 2026, 01:39 PM UTC
Customers are unable to create new Dedicated Deployments in the Managed Inference service.
- resolved May 05, 2026, 06:17 PM UTC
Customers are now able to create new Dedicated Deployments in the Managed Inference service.
Minor May 5, 2026 [Serverless SQL DB] - [fr-par] DB/API unavailable 2d 1h Serverless-Database
Started May 05, 2026, 12:58 PM UTC· resolved May 07, 2026, 02:05 PM UTC
- investigating May 05, 2026, 12:58 PM UTC
Customers may experience unavailability on Serverless SQL DB in the fr-par region.
- resolved May 07, 2026, 02:05 PM UTC
This incident has been resolved.
Major May 5, 2026 [LBAS] - [PAR1] - Private Networks issue on many LBs 1d Load Balancer
Started May 05, 2026, 12:23 PM UTC· resolved May 06, 2026, 12:51 PM UTC
- investigating May 05, 2026, 12:23 PM UTC
We are currently observing connectivity issues with Load Balancers caused by a partial outage on an internal dependency in the fr-par-1 region.
- investigating May 05, 2026, 01:27 PM UTC
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
- investigating May 05, 2026, 03:01 PM UTC
Data Warehouse experiencing issues creating new deployments
- resolved May 06, 2026, 12:51 PM UTC
The issue has been fixed. Everything is back to normal since yesterday at 8:30 PM. If you are still encountering an issue please contact our support team.
Major May 5, 2026 [WBHE] - Dedibox to Element migrations are failing 5d 22h Hosting
Started May 05, 2026, 10:45 AM UTC· resolved May 11, 2026, 08:47 AM UTC
- investigating May 05, 2026, 10:45 AM UTC
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.
- resolved May 11, 2026, 08:47 AM UTC
This incident has been resolved.
Major May 5, 2026 [API Gateway] - [pl-waw] Connectivity issues 11m APIs
Started May 05, 2026, 08:21 AM UTC· resolved May 05, 2026, 08:33 AM UTC
- investigating May 05, 2026, 08:21 AM UTC
Customers may experience connectivity issues with their APIs in the pl-waw region.
- resolved May 05, 2026, 08:33 AM UTC
This incident has been resolved.
Critical May 5, 2026 [Domain Names] All BookMyName services unavailable 1d 9h BookMyName, Domains, Domains
Started May 05, 2026, 06:55 AM UTC· resolved May 06, 2026, 04:38 PM UTC
- investigating May 05, 2026, 08:34 AM UTC
All BookMyName services are unavailable, and we are currently investigating the root cause.
- investigating May 05, 2026, 09:11 AM UTC
We are continuing to investigate this issue.
- investigating May 05, 2026, 11:07 AM UTC
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.
- investigating May 05, 2026, 03:31 PM UTC
À 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.
- monitoring May 05, 2026, 08:00 PM UTC
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.
- monitoring May 06, 2026, 12:16 PM UTC
Nos équipes ont identifié et isolé la cause de l'incident affectant les informations de contact de vos noms de domaine. L'ensemble des clients concernés a été contacté individuellement. Le service est pleinement rétabli depuis hier à 22h00 (CET). Vous pouvez désormais administrer vos noms de domaine normalement. Veuillez noter toutefois que certaines fonctionnalités secondaires restent temporairement indisponibles ; nous prévoyons leur réactivation progressive dans les prochaines heures. Un rapport d'incident détaillé vous sera adressé prochainement pour vous apporter toute la transparence nécessaire sur cet événement. Nos équipes restent à votre entière disposition pour toute question complémentaire via notre support technique ou vos interlocuteurs habituels. —-- Our teams have identified and isolated the root cause of the incident affecting your domain name contact information. All impacted customers have been contacted individually. Service has been fully restored since yesterday at 10:00 PM (CET). You can now manage your domain names as usual. However, please note, that some secondary features remain temporarily unavailable; we expect to reactivate them progressively over the coming hours. A detailed incident report will be sent to you shortly to provide full transparency regarding this event. Our teams remain at your entire disposal for any further questions via our technical support or your usual points of contact.
- monitoring May 06, 2026, 02:19 PM UTC
We are continuing to monitor for any further issues.
- resolved May 06, 2026, 04:38 PM UTC
L'incident est désormais résolu. Pour plus d'information concernant sa résolution, le rapport d'incident est disponible : https://security.scaleway.com/?tcuUid=77cb65ef-456b-45a5-99b7-27eae316a112 Veuillez toutefois noter que la réinitialisation de mot de passe est temporairement indisponible. Si vous souhaitez modifier votre mot de passe, nous vous invitons à contacter notre support afin d'effectuer cette opération. Nos équipes restent à votre entière disposition pour toute question complémentaire via notre support technique ou vos interlocuteurs habituels. —-- The incident is now resolved. For more information about its resolution, the incident report is available : https://security.scaleway.com/?tcuUid=77cb65ef-456b-45a5-99b7-27eae316a112 Please be advised that the password reset function is currently disabled. Should you wish to modify your password, we invite you to reach out to our support for assistance. Our teams remain at your entire disposal for any further questions via our technical support or your usual points of contact.
Minor May 4, 2026 [API Gateway] - [it-mil-1] DNS resolving issues 22d APIs
Started May 04, 2026, 12:54 PM UTC· resolved May 26, 2026, 01:32 PM UTC
- identified May 04, 2026, 12:54 PM UTC
Customers may experience issues resulting using our APIs in the it-mil-1 region.
- resolved May 26, 2026, 01:32 PM UTC
This incident has been resolved.
Minor May 4, 2026 [AGWX] - [it-mil-1] - DNS resolving issues 13m Databases, IAM, Load Balancer, Messaging and Queuing and 2 more
Started May 04, 2026, 12:53 PM UTC· resolved May 04, 2026, 01:06 PM UTC
- investigating May 04, 2026, 12:53 PM UTC
Customers may experience DNS resolving issues resulting in service unavailability on API Gateway in the it-mil-1 region.
Minor May 4, 2026 [Billing] - [fr-par/global] April to May cutoff delay 7h 48m Billing
Started May 04, 2026, 06:43 AM UTC· resolved May 04, 2026, 02:32 PM UTC
- identified May 04, 2026, 06:43 AM UTC
Customers may experience missing or incorrect billing data for May due to a delay in the monthly cutoff process.
- identified May 04, 2026, 06:45 AM UTC
Customers may experience missing or incorrect billing data for May due to a delay in the monthly cutoff process. Expect May consumptions and draft bill amounts to be up-to-date and reliable before 12:00 Paris time
- investigating May 04, 2026, 06:46 AM UTC
We are currently investigating this issue.
- identified May 04, 2026, 06:49 AM UTC
Customers may experience missing or incorrect billing data for May due to a delay in the monthly cutoff process. Expect May consumptions and draft bill amounts to be up-to-date and reliable before 12:00 Paris time
- resolved May 04, 2026, 02:32 PM UTC
This incident has been resolved.