THIS IS A SCHEDULED EVENT Jun <var data-var='date'>9</var>, <var data-var='time'>06:00</var> - <var data-var='time'>10:00</var> CEST May <var data-var='date'>22</var>, <var data-var='time'>14:46</var> CEST Scheduled - Dear Customer, As part of maintenance on our network infrastructure, our network team will be restarting a router located in the DC2 datacenter (s101-2.dc2). This maintenance is scheduled for Tuesday, June 9, 2026, between 6:00 AM and 10:00 AM (CEST). The equipment will be restarted during this maintenance window. A service interruption of approximately 15 minutes may be experienced during the work. In addition, occasional network disruptions may occur throughout the maintenance window. All services will be automatically restored upon completion of this operation. Thank you for your understanding. Best regards, The Scaleway Team

[Network infrastructure] - Datacenter DC2 (s101-2) - Router reboot

THIS IS A SCHEDULED EVENT Jun <var data-var='date'>3</var>, <var data-var='time'>09:00</var> - <var data-var='time'>18:00</var> CEST May <var data-var='date'>21</var>, <var data-var='time'>18:07</var> CEST Scheduled - Connection losses. A few seconds of downtime for High Availability and Cluster configurations. Up to 1 minute of downtime for Standalone configurations.

[REDIS] Scheduled Maintenance

May <var data-var='date'>23</var>, <var data-var='time'>14:40</var> CEST Resolved - Switchover to main power has been completed successfully. We are back to a nominal state. May <var data-var='date'>23</var>, <var data-var='time'>13:41</var> CEST Update - Datacenter teams are now confident the batteries were involved in the initial incident, they will attempt to switch back to main power at 14:30 CEST. May <var data-var='date'>23</var>, <var data-var='time'>13:09</var> CEST Update - Batteries replacement has been completed on all 4 electrical paths. Removed batteries are under tests and investigations to confirm their involvement in the initial incident. No more action on production expected for now. We are still on power generators for the time being. May <var data-var='date'>23</var>, <var data-var='time'>11:56</var> CEST Update - Batteries replacement is ongoing, 1 of the 4 electrical paths has been done (no impact). Datacenter teams will proceed with the next paths. May <var data-var='date'>22</var>, <var data-var='time'>22:30</var> CEST Update - The datacenter provider has planned an intervention on Saturday at 10:30 CEST to replace batteries on the electrical paths that had issues today. This operation will be done live and should have no impact. Once replaced, old batteries will be inspected and tested to confirm they were the cause of the incident. Power will be kept on generators during this operation and after until the root cause is fully confirmed May <var data-var='date'>22</var>, <var data-var='time'>16:57</var> CEST Update - Updated status for impacted products: - Object Storage: Everything back to normal - Serveless containers and functions: Everything is back to normal. - File: some instances may encounter troubles with their File Storage, we invite customers to restart their instances/nodes if affected As the failover malfunction has not been diagnosed at this time, our datacenter manager will keep the affected elements under a generator. May <var data-var='date'>22</var>, <var data-var='time'>16:30</var> CEST Update - Updated status for impacted products: - Object Storage: still some latency issues and timeout on connecting some buckets - Serveless containers and functions: Everything is back to normal. Situation recovered and stable since 02:40 PM - File Storage: some instances may encounter troubles with their File Storage, we invite customers to restart their instances/nodes if affected May <var data-var='date'>22</var>, <var data-var='time'>14:26</var> CEST Update - Updated status for impacted products: - Kapsule: everything back to normal - Databases: everything back to normal - Object Storage: still some latency issues and timeout on connecting some buckets - Serveless containers and functions: might face connection timeout issues when contacting their applications - File Storage: some instances may encounter troubles with their File Storage, we invite customers to restart their instances/nodes if affected May <var data-var='date'>22</var>, <var data-var='time'>13:25</var> CEST Update - Clarification: only network rooms are running on power generators, with enough fuel for a few days May <var data-var='date'>22</var>, <var data-var='time'>13:10</var> CEST Monitoring - Updated status for impacted products: - Instances: everything back to normal - Kapsule: same status - Databases: same status - Object Storage: same status - Serveless containers and functions: might face connection timeout issues when contacting their applications May <var data-var='date'>22</var>, <var data-var='time'>12:44</var> CEST Update - As the power failure root cause is not yet understood (datacenter is investigating with its providers), we encourage you to shift workload on alternatives regions/AZ if possible. May <var data-var='date'>22</var>, <var data-var='time'>12:31</var> CEST Identified - Datacenter informs us that we are running on power generators for now until the root cause is identified May <var data-var='date'>22</var>, <var data-var='time'>12:28</var> CEST Update - Teams are working on the recovery. Here is the status of impacted products: - Instances: you may encounter issues with l_ssd/block snapshots or volumes - Kapsule: Control planes are reachable and in nominal state, you may need to verify that your controllers reconnected properly on the apiservers. You may have experienced node replacement due to the autoheal or autoscaling process, this may delay volume re-attachments. - Databases: snapshots may be blocked, some failovers have been started for HA - Object storage: you may encounter some latencies May <var data-var='date'>22</var>, <var data-var='time'>12:24</var> CEST Update - Datacenter hosting FR-PAR-2 availability zone occured a complete power failure in operator rooms during a planned datacenter maintenance. Both operator rooms (network connectivity) were powerless for a few minutes leading to a complete isolation of the availability zone during the issue. We are investigating with the datacenter provider to understand the root cause.” May <var data-var='date'>22</var>, <var data-var='time'>11:42</var> CEST Monitoring - Most services recovered and our teams are mobilized to recover the rest on fr-par-2. Root cause is a power issue in datacenter. Other service on par1 & par3 were impacted during the service transition. May <var data-var='date'>22</var>, <var data-var='time'>11:23</var> CEST Update - The issue is impacting multiple products on FR-PAR. May <var data-var='date'>22</var>, <var data-var='time'>11:21</var> CEST Update - We are continuing to investigate this issue and searching for the root cause. May <var data-var='date'>22</var>, <var data-var='time'>11:21</var> CEST Investigating - We are currently experiencing connection and network issues in the FR‑PAR region, affecting all FR‑PAR availability zones on Scaleway as well as DC5 on Dedibox.

FR-PAR-2 connectivity loss

May <var data-var='date'>22</var>, <var data-var='time'>13:45</var> CEST Resolved - 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. May <var data-var='date'>22</var>, <var data-var='time'>11:17</var> CEST Update - We are continuing to investigate this issue. May <var data-var='date'>22</var>, <var data-var='time'>11:16</var> CEST Investigating - We are currently investigating on that incident.

Kafka cluster not reachable - Connection to Kafka clusters fails.

May <var data-var='date'>20</var>, <var data-var='time'>10:15</var> CEST Resolved - This incident has been resolved. May <var data-var='date'>19</var>, <var data-var='time'>14:34</var> CEST Investigating - Customers may experience Network issues contacting our APIs. We are currently investigating this issue.

[API Gateway] - [world] APIs instabilities

May <var data-var='date'>19</var>, <var data-var='time'>14:22</var> CEST Resolved - This incident has been resolved. May <var data-var='date'>19</var>, <var data-var='time'>11:19</var> CEST Monitoring - 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. May <var data-var='date'>19</var>, <var data-var='time'>11:07</var> CEST Investigating - 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

[Identity and Access Management] - [world] API unavailable

May <var data-var='date'>19</var>, <var data-var='time'>14:14</var> CEST Resolved - This incident has been resolved. May <var data-var='date'>19</var>, <var data-var='time'>11:33</var> CEST Investigating - Customers may experience issues caused by a PostgreSQL LISTEN/NOTIFY bug in fr-par-1. Asahi and DevOS configuration/installation workflows on Mac-Mini servers are currently unable to complete & will result in retry. This may cause machine to temporarily end up in error state or installation to take longer than usual. We are working to restablish the service as fast as possible.

[Apple Silicon] - [fr-par-1] Increased delivery & installation time for Apple Silicon machines

May <var data-var='date'>18</var>, <var data-var='time'>17:33</var> CEST Resolved - This incident has been resolved. May <var data-var='date'>18</var>, <var data-var='time'>15:07</var> CEST Investigating - Customers may encounter 403 or 500 errors when querying the service. The root cause has been identified, and we're working on a fix.

Generative API instabilities

May <var data-var='date'>18</var>, <var data-var='time'>15:56</var> CEST Resolved - The incident affected the API on our DNS Management for Elements. We had an API answer time issue between 14:43 and 14:51.

[DNSE] - API slow

May <var data-var='date'>18</var>, <var data-var='time'>13:09</var> CEST Resolved - This incident has been resolved. May <var data-var='date'>15</var>, <var data-var='time'>10:41</var> CEST Investigating - 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.

[KUBE] - [it-mil] - creating/upgrade cluster issue

May <var data-var='date'>15</var>, <var data-var='time'>11:53</var> CEST Resolved - The fix have been deployed in every region May <var data-var='date'> 6</var>, <var data-var='time'>16:03</var> CEST Update - A fix for fr-par and pl-waw region have been deployed, next regions will follow soon Mar <var data-var='date'>24</var>, <var data-var='time'>15:27</var> CET 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.

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

May <var data-var='date'>13</var>, <var data-var='time'>12:28</var> CEST Resolved - This incident has been resolved. May <var data-var='date'>13</var>, <var data-var='time'>09:57</var> CEST Investigating - 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

[Instance Orchestration] - [fr-par-2] No public IPv4 available

May <var data-var='date'>11</var>, <var data-var='time'>17:45</var> CEST Completed - The scheduled maintenance has been completed. May <var data-var='date'>11</var>, <var data-var='time'>09:45</var> CEST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'>11</var>, <var data-var='time'>09:41</var> CEST Scheduled - Following electrical maintenance performed by our data center provider on AZ NL-AMS-2, the servers will be on a single power supply this Monday, May 11, 2026. No impact is expected on your machines. Service is expected to return to normal around 5:00 p.m. CEST.

[Elastic-Metal] - NL-AMS-2 - Electrical maintenance on power redundancy

May <var data-var='date'>11</var>, <var data-var='time'>17:38</var> CEST Resolved - This incident has been resolved. May <var data-var='date'>11</var>, <var data-var='time'>17:19</var> CEST Investigating - Customers may experience connectivity issues on the WebHosting platform pf-1005. Our teams are working to resolve the issue.

[WebHosting Elements] - [fr-par] Platform connectivity issues

May <var data-var='date'>11</var>, <var data-var='time'>14:39</var> CEST Monitoring - 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. May <var data-var='date'>11</var>, <var data-var='time'>13:45</var> CEST Investigating - 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.

[OBJS] - [nl-AMS]  Object Storage availability issues on AMS

May <var data-var='date'>11</var>, <var data-var='time'>10:47</var> CEST Resolved - This incident has been resolved. May <var data-var='date'> 5</var>, <var data-var='time'>12:45</var> 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.

[WBHE] - Dedibox to Element migrations are failing

May <var data-var='date'> 7</var>, <var data-var='time'>16:05</var> CEST Resolved - This incident has been resolved. May <var data-var='date'> 5</var>, <var data-var='time'>14:58</var> CEST Investigating - Customers may experience unavailability on Serverless SQL DB in the fr-par region.

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

May <var data-var='date'> 6</var>, <var data-var='time'>19:00</var> CEST Completed - The scheduled maintenance has been completed. May <var data-var='date'> 5</var>, <var data-var='time'>10:00</var> CEST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>21</var>, <var data-var='time'>17:24</var> 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.

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

May <var data-var='date'> 6</var>, <var data-var='time'>18:38</var> CEST 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 <var data-var='date'> 6</var>, <var data-var='time'>16:19</var> CEST Update - We are continuing to monitor for any further issues. May <var data-var='date'> 6</var>, <var data-var='time'>14:16</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>22:00</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>17:31</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>13:07</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>11:11</var> CEST Update - We are continuing to investigate this issue. May <var data-var='date'> 5</var>, <var data-var='time'>08:55</var> CEST Investigating - All BookMyName services are unavailable, and we are currently investigating the root cause. Domain management on Scaleway and Dedibox are also impacted.

[Domain Names] All BookMyName services unavailable

May <var data-var='date'> 6</var>, <var data-var='time'>16:09</var> CEST Resolved - This incident has been resolved. Apr <var data-var='date'>30</var>, <var data-var='time'>18:03</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>30</var>, <var data-var='time'>17:46</var> 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 <var data-var='date'>30</var>, <var data-var='time'>17:15</var> 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

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

May <var data-var='date'> 6</var>, <var data-var='time'>16:08</var> CEST Resolved - This incident has been resolved. Apr <var data-var='date'>30</var>, <var data-var='time'>11:48</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>30</var>, <var data-var='time'>11:48</var> 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 <var data-var='date'>30</var>, <var data-var='time'>11:32</var> 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.

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

May <var data-var='date'> 6</var>, <var data-var='time'>16:05</var> CEST Resolved - This incident has been resolved. May <var data-var='date'> 6</var>, <var data-var='time'>15:39</var> 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. Apr <var data-var='date'>20</var>, <var data-var='time'>09:43</var> 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.

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

May <var data-var='date'> 6</var>, <var data-var='time'>15:37</var> CEST Resolved - This incident has been resolved. Apr <var data-var='date'>28</var>, <var data-var='time'>14:10</var> CEST Monitoring - Dedibox customers in rack DC5/S1/C57 may experienced network connectivity issues on the rpn network due to a switch reboot.

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

May <var data-var='date'> 6</var>, <var data-var='time'>15:36</var> CEST Resolved - This incident has been resolved. May <var data-var='date'> 3</var>, <var data-var='time'>15:41</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'> 3</var>, <var data-var='time'>14:41</var> CEST Update - The engineers on our Edge Services team are still investigating the situation. May <var data-var='date'> 3</var>, <var data-var='time'>13:21</var> 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.

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

May <var data-var='date'> 6</var>, <var data-var='time'>14:51</var> CEST 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 <var data-var='date'> 5</var>, <var data-var='time'>17:01</var> CEST Update - Data Warehouse experiencing issues creating new deployments May <var data-var='date'> 5</var>, <var data-var='time'>15:27</var> 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 <var data-var='date'> 5</var>, <var data-var='time'>14:23</var> 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.

Is Scaleway down?

Scaleway status is DEGRADED

Components with issues

Lastest published events

FR-PAR-2 connectivity loss

Kafka cluster not reachable - Connection to Kafka clusters fails.

[API Gateway] - [world] APIs instabilities

Scaleway Services, Components and Regions

Recent Scaleway events

[Network infrastructure] - Datacenter DC2 (s101-2) - Router reboot

[REDIS] Scheduled Maintenance

FR-PAR-2 connectivity loss

Kafka cluster not reachable - Connection to Kafka clusters fails.

[API Gateway] - [world] APIs instabilities

[Identity and Access Management] - [world] API unavailable

Get your FREE account now,
5 monitors included!

Is Scaleway down?

Scaleway status is DEGRADED

Components with issues

Lastest published events

FR-PAR-2 connectivity loss

Kafka cluster not reachable - Connection to Kafka clusters fails.

[API Gateway] - [world] APIs instabilities

Scaleway Services, Components and Regions

Recent Scaleway events

[Network infrastructure] - Datacenter DC2 (s101-2) - Router reboot

[REDIS] Scheduled Maintenance

FR-PAR-2 connectivity loss

Kafka cluster not reachable - Connection to Kafka clusters fails.

[API Gateway] - [world] APIs instabilities

[Identity and Access Management] - [world] API unavailable

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!