Scaleway Status

Status impact color legend

Black impact: None
Yellow impact: Minor
Red impact: Major
Blue impact: Maintenance

[OBJS] - [world] - Failures on ranged request on SSE enabled objects

Update - A fix for fr-par and pl-waw region have been deployed, next regions will follow soon
May 06, 2026 - 16:03 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

[Redis] - [fr-par, nl-ams, pl-war] Failing provisioning and workflows

Identified - Customers may experience failing workflows on Redis such as provisioning new instances
May 05, 2026 - 18:53 CEST

[Serverless SQL DB] - [fr-par] DB/API unavailable

Investigating - Customers may experience unavailability on Serverless SQL DB in the fr-par region.
May 05, 2026 - 14:58 CEST

[WBHE] - Dedibox to Element migrations are failing

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

[WEBHOSTING] SMTP/51.159.208.135 blacklisted on Microsoft/Outlook from classic webhosting service

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

[API Gateway] - [it-mil-1] DNS resolving issues

Identified - Customers may experience issues resulting using our APIs in the it-mil-1 region.
May 04, 2026 - 14:54 CEST

SMS Routing to US Numbers

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

Identified - The issue has been identified and a fix is being implemented.
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

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 Operational

Apple Silicon Operational

Billing Operational

Block Storage 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

Generative API Operational

IAM Operational

Instances Operational

IoT Hub Operational

Jobs Operational

Kafka Operational

Kubernetes Kapsule Operational

Load Balancer Operational

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 Operational

RPN Degraded Performance

Dedibox Console Operational

Dedibox VPS Operational

Dedibox - Datacenters Operational

DC1 Operational

DC2 Operational

DC3 Operational

DC4 Operational

DC5 Operational

AMS Operational

Miscellaneous Operational

Excellence Operational

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

Past Incidents

May 7, 2026

No incidents reported today.

May 6, 2026

[Serverless Functions] - [fr-par] - mandatory operation to release VPC routing

Completed - The scheduled maintenance has been completed.
May 6, 19:00 CEST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 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.
Apr 21, 17:24 CEST

[Domain Names] All BookMyName services unavailable

Resolved - 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.
May 6, 18:38 CEST

Update - We are continuing to monitor for any further issues.
May 6, 16:19 CEST

Update - 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.
May 6, 14:16 CEST

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 5, 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 5, 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 5, 13:07 CEST

Update - We are continuing to investigate this issue.
May 5, 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 5, 08:55 CEST

[Block Storage] - [fr-par-1] Snapshot API call timeouts

Resolved - This incident has been resolved.
May 6, 16:09 CEST

Monitoring - A fix has been implemented and we are monitoring the results.
Apr 30, 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, 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, 17:15 CEST

[Object Storage] - [it-mil] S3 frontal requests failures

Resolved - This incident has been resolved.
May 6, 16:08 CEST

Monitoring - A fix has been implemented and we are monitoring the results.
Apr 30, 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, 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, 11:32 CEST

[PAYM] - [all] - Issues adding cards via Stripe

Resolved - This incident has been resolved.
May 6, 16:05 CEST

Update - The issue has been fixed.
If you are still encountering an issue with Stripe payment, it is related to your bank. Please contact them to unlock the situation and allow the payment to go through Stripe. Or add another payment method.
May 6, 15:39 CEST

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, 09:43 CEST

[Network infrastructure] - DC5 - RPN Switch reboot in rack DC5/S1/C57

Resolved - This incident has been resolved.
May 6, 15:37 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, 14:10 CEST

[EDGE SERVICES] - Edge Services is currently unavailable from the outside

Resolved - This incident has been resolved.
May 6, 15:36 CEST

Monitoring - A fix has been implemented and we are monitoring the results.
May 3, 15:41 CEST

Update - The engineers on our Edge Services team are still investigating the situation.
May 3, 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 3, 13:21 CEST

[LBAS] - [PAR1] - Private Networks issue on many LBs

Resolved - 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.
May 6, 14:51 CEST

Update - Data Warehouse experiencing issues creating new deployments
May 5, 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 5, 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 5, 14:23 CEST

[Cockpit] - [nl-ams/pl-waw] Elevated error rates on metrics and logs

Resolved - 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.
May 6, 14:49 CEST

Investigating - Customers may experience elevated error rates on metrics and logs in Cockpit on the nl-ams and pl-waw regions.
May 6, 11:06 CEST

[Dedibox RPN] - [DC5 room 1 rack D13 block F] - RPN switch down

Resolved - 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.
May 6, 11:01 CEST

Investigating - 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.
May 6, 09:44 CEST

[Kapsule] fr-par Control Plane Infrastructure Upgrade

Completed - The scheduled maintenance has been completed.
May 6, 09:49 CEST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 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 4, 17:03 CEST

May 5, 2026

[DNS Management for Elements] - Partial outage on DNS record management

Resolved - 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
May 5, 22:30 CEST

[Managed Inference] - [fr-par] Dedicated Deployments unavailability

Resolved - Customers are now able to create new Dedicated Deployments in the Managed Inference service.
May 5, 20:17 CEST

Identified - Customers are unable to create new Dedicated Deployments in the Managed Inference service.
May 5, 15:39 CEST

[DDBX] - [world] - Order/renewal validation is broken

Resolved - This incident has been resolved.
May 5, 18:50 CEST

Investigating - 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.
May 5, 17:55 CEST

[API Gateway] - [pl-waw] Connectivity issues

Resolved - This incident has been resolved.
May 5, 10:33 CEST

Investigating - Customers may experience connectivity issues with their APIs in the pl-waw region.
May 5, 10:21 CEST

May 4, 2026

[Billing] - [fr-par/global] April to May cutoff delay

Resolved - This incident has been resolved.
May 4, 16:32 CEST

Identified - 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
May 4, 08:49 CEST

Investigating - We are currently investigating this issue.
May 4, 08:46 CEST

Update - 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
May 4, 08:45 CEST

Identified - Customers may experience missing or incorrect billing data for May due to a delay in the monthly cutoff process.
May 4, 08:43 CEST

[Network infrastructure] - DC2 - Public switch in S301/D19 is unreachable

Resolved - This incident has been resolved.
May 4, 14:25 CEST

Investigating - Customers may experience a partial outage on public connectivity for servers located in this rack.
We are currently investigating this issue.
Apr 27, 09:51 CEST

[Billing] - [fr-par/global] April to May cutoff delay

Resolved - This incident has been resolved.
May 4, 13:44 CEST

Investigating - Customers may experience missing or incorrect billing data for May due to a delay in the monthly cutoff process.
May 3, 21:56 CEST

May 3, 2026

May 2, 2026

No incidents reported.

May 1, 2026

[INSTANCE] - [ALL REGION] Instance creation failure from console

Resolved - This incident has been resolved.
May 1, 10:36 CEST

Monitoring - A fix has been implemented and we are monitoring the results.
May 1, 10:22 CEST

Identified - A fix has been implemented and we are monitoring the results
May 1, 10:21 CEST

Investigating - Due to an internal issue, it is currently not possible to create new instances across all regions from the console.
However, you can create them using the Scaleway CLI available here: https://cli.scaleway.com/instance/
May 1, 07:26 CEST

Apr 30, 2026

[Object Storage] - [fr-par] Timeouts on object uploads

Resolved - This incident has been resolved.
Apr 30, 14:57 CEST

Monitoring - We have implemented corrective measures. Performance should return to normal. We have planned further actions to resolve the issue long-term.
Apr 22, 17:41 CEST

Update - We are continuing to investigate this issue.
Apr 22, 14:39 CEST

Investigating - Customers may experience timeouts when uploading objects to Object Storage in the fr-par region due to an issue with an internal component.
Apr 22, 13:51 CEST

[Network infrastructure] - nl-ams-2 - Reboot of elastic metal top of rack switch

Resolved - At 10h43 CET, customers may have experienced network interruptions on Elastic Metal servers located in rack 430B/110 in nl-ams-2
Apr 30, 11:55 CEST

[E-mail Gateway] - [World] - Delays sending emails to ProtonMail

Resolved - This incident has been resolved.
Apr 30, 10:58 CEST

Investigating - The emails that are sent to ProtonMail (including the emails sent to a custom domain associated to ProtonMail) are processed very slowly.
Apr 29, 11:11 CEST

Apr 29, 2026

[Serverless Functions] - [pl-waw/nl-ams] - mandatory operation to release VPC routing

Completed - The scheduled maintenance has been completed.
Apr 29, 19:00 CEST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 28, 10:00 CEST

Scheduled - From April 28st to April 29th (between 10 AM and 7:00 PM CEST), we will perform a mandatory operation in the pl-waw and nl-ams regions to release VPC routing.

Over the course of these two days, changes will be applied to all Serverless Functions namespaces in the pl-waw and nl-ams regions.

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.
Apr 21, 17:22 CEST

Apr 28, 2026

Maintenance on Dedibox VPS

Completed - The scheduled maintenance has been completed.
Apr 28, 22:00 CEST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 28, 16:00 CEST

Scheduled - Physical maintenance in Amsterdam is scheduled for Tuesday the 28th of April, from 16:00 to 22:00 CEST. Downtime is expected during this operation.
Apr 27, 10:23 CEST

[Maintenance]-scheduled maintenance on API in it-mil

Completed - The scheduled maintenance has been completed.
Apr 28, 16:00 CEST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 28, 14:00 CEST

Scheduled - A maintenance operation on Kafka in Milan API, short time unavailability during this period on API. Active Kafka clusters won't be affected
Zone: it-mil
Apr 21, 15:38 CEST

[Serverless Functions] - [fr-par/nl-ams/pl-waw] DNS resolution failures for all functions

Resolved - The root cause has been fixed: all functions now have a working DNS again. The incident is now closed.

Impacted functions were:

- on fr-par, only functions not attached to a private network, that belong to a namespace created after 2026-04-28 8:00 AM UTC, until 1:05 PM UTC.
- on nl-ams, all functions not attached to a private network, between 8:41 AM UTC and 1:46 PM UTC
- on pl-waw, all functions not attached to a private network, between 9:30 AM UTC and 1:05 PM UTC

The incident on nl-ams and pl-waw is related to the scheduled maintenance https://status.scaleway.com/incidents/zrhfpqjvjyrl. A mismatch between DNS service IPs caused the issue.

We deeply apologize for the inconvenience.
Apr 28, 15:50 CEST

Update - After investigation, this also affects functions created on new namespaces on fr-par.
Apr 28, 14:16 CEST

Update - We are continuing to investigate this issue.
Apr 28, 14:11 CEST

Investigating - Customers may experience DNS resolution failures for their Serverless Functions in the nl-ams and pl-waw regions, due to an error that happened during the scheduled maintenance: https://status.scaleway.com/incidents/qhh06fhhn47r.

Errors for clients might look like: "lookup [...] on 10.32.15.25:53: read udp 100.96.xx.xx:xx->10.32.15.25:53: i/o timeout".

We have identified the root cause. Sorry about any inconvenience.
Apr 28, 14:06 CEST

[SAAGIE - Product-1-ACO] - - Kubernetes cluster upgrade v1.33

Completed - The scheduled maintenance has been completed.
Apr 28, 12:35 CEST

Verifying - Verification is currently underway for the maintenance items.
Apr 28, 12:35 CEST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 28, 12:00 CEST

Scheduled - A maintenance operation is scheduled for Tuesday, April 28, 2026, from 12:00 AM to 13:00 PM.

This intervention aims to upgrade the Kubernetes platform to version v1.33 on SAAGIE infrastucture.

During this period, temporary service disruptions or interruptions may occur.

We recommend that you take the necessary measures to minimize the impact on your activities.

Our teams remain fully mobilized to ensure the smooth execution of this operation and a return to normal service as quickly as possible.

Thank you for your understanding.

Best regards,
Apr 27, 09:55 CEST

Apr 27, 2026

[BareMetal API] IPMI calls timeout issue

Resolved - This incident has been resolved.
Apr 27, 17:15 CEST

Investigating - Customers may experience timeouts when performing IPMI calls, including stop, start, and reboot actions, on BareMetal servers.
Apr 27, 11:18 CEST

[DC5] Private switch issue in room 1 rack c57 unreachable

Resolved - This incident has been resolved.
Apr 27, 14:19 CEST

Investigating - We have detected a switch down in room 1 rack c57 in DC5
Servers in that rack currently have no private network access and are unreachable.

27.04.2026 10h00 UTC
The issue has been forwarded to our team for resolution.
Apr 27, 10:19 CEST

[SAAGIE - Product-2-BOU] - Kubernetes cluster upgrade v1.33

Completed - The scheduled maintenance has been completed.
Apr 27, 11:45 CEST

Verifying - Verification is currently underway for the maintenance items.
Apr 27, 11:45 CEST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 27, 11:00 CEST

Scheduled - A maintenance operation is scheduled for Monday, April 27, 2026, from 11:00 AM to 12:00 PM.

This intervention aims to upgrade the Kubernetes platform to version v1.33 on SAAGIE infrastucture.

During this period, temporary service disruptions or interruptions may occur.

We recommend that you take the necessary measures to minimize the impact on your activities.

Our teams remain fully mobilized to ensure the smooth execution of this operation and a return to normal service as quickly as possible.

Thank you for your understanding.
Apr 27, 09:51 CEST

[PAYMENT] - Payment result handling issue

Resolved - This incident has been resolved.
Apr 27, 10:26 CEST

Investigating - Some customers paying by card may experience a display issue where the invoice shows "unpaid" even though it has been paid.

We apologize for any inconvenience this may cause.
Apr 2, 15:55 CEST

[Network infrastructure] - DC5 - rpn switch in room 1 rack c57 unreachable

Resolved - This incident has been resolved.
Apr 27, 09:49 CEST

Investigating - Customers may experience network connectivity issues on servers attached to the rpn switch located in room 1 rack c57 in DC5.
Apr 27, 09:24 CEST

Apr 26, 2026

No incidents reported.

Apr 25, 2026

No incidents reported.

Apr 24, 2026

No incidents reported.

Apr 23, 2026

[REGX] - [fr-par] - timeout for some requests

Resolved - This incident has been resolved.
Apr 23, 16:07 CEST

Update - We are continuing to monitor for any further issues.
Apr 23, 15:15 CEST

Monitoring - Due to a database issue, some requests to the registry API did timeout
Apr 23, 15:04 CEST

[DC3] <public/private> switch issue in DC3;4 4-6 ;F2

Resolved - This incident has been resolved.
Apr 23, 10:33 CEST

Investigating - We have detected a switch down in DC3;4 4-6;F2.
Servers in that rack currently have no public network access and are unreachable.

===================

23/042026 10h20 UTC
The issue has been forwarded to our team for resolution.
Apr 23, 10:32 CEST