Is Scaleway Down Right Now? Discover if there is an ongoing service outage.

A Dedibox server in the DC2 room 101- g23-8 is currently experiencing an outage. The issue is suspected to be related to a power supply unit (PSU) failure. This may result in the server being unavailable until the issue is resolved.

Between 24 July 2025 at 10:13 UTC and 28 July 2025 at 13:00 UTC, some clients in the NL-AMS Region experienced issues accessing or viewing the logs of their Serverless Jobs. Logs from jobs executed during this period may be temporarily or permanently inaccessible.

Another recurrence of the issue https://status.scaleway.com/incidents/kzqlg7926xqh happened between 08:06 and 08:32 UTC. A faulty internal dependency is causing delays in our container (and other resources) deployment process. Retrying now might solve the issue. Everything is ok now, but we are reopening the status as the concerned team is working on it. Sorry for any inconvenience.

Due to an internal issue, it is currently not possible to create new instances in the NL-AMS-1 region. This may affect the scalability and deployment of your services.

Since this morning, customers have been experiencing delays in the creation of serverless containers in the fr-par region. This issue may result in the inability to deploy new containers and potential delays in service availability.

Our cPanel platforms are currently experiencing an issue where websites using Cloudflare are displaying the error "421 Misdirected Request". This may result in websites being inaccessible or experiencing intermittent downtime.

Due to circumstances beyond our control, support will be exceptionally unavailable from 6 PM tonight until 10 PM. We apologize for this inconvenience.

This incident has been resolved.

**Short Description:** On July 25, 2025, at 15:44 UTC, there were issues with the deployment or reconfiguration of MongoDB services in the FR-PAR region. This may have caused delays or failures in the creation or modification of MongoDB instances, potentially affecting the availability and performance of your databases.

Short description: On July 25th, at 15:42 UTC, switches in rack D14 experienced a reboot, impacting public services for racks D14 to D16 and rpn services for rack D14. Services were restored at 15:47 UTC. Note : incident is already over and cause it most likely power failure in the rack as both switch rebooted at the same time

Between 9:15 and 9:30, the VPC API experienced a downtime in the Paris region. T This incident affected all operations related to IP address booking on IPAM and all operations on VPCs and private networks.

Containers and Functions can't start or scale Since 25th of July 2025, 7:29:49 AM UTC, it is not possible to start or scale VPC-enabled functions and containers in the Paris region. This may affect the availability and scalability of your applications.

Since 20/07 a client generated a massive purge of his volumes. This impacted our purge system : As it takes time to purge volumes the job is creating async tasks for already scheduled jobs. This table size increased DB response time and impacted API response time. The situation is stable and we are working in removing duplicated jobs

Due to an internal issue, the latest node versions (1.32.[4-7], 1.31.[8-11], 1.30.[12-14]) are currently not provisioning in every region. This incident is expected to be fully mitigated by 17:30. This may impact the creation of new nodes and the scaling of existing pools updated to latest patch versions.

We have detected that public switch was down in DC2 Room 101 Rack G32 Servers in that rack currently have no network access and are unreachable.

It is currently not possible to deploy new Redis instances or perform actions on existing ones. Our teams are currently investigating the situation. We will update this status as soon as we have more information.

We experienced connectivity issues with some GPU Instances within the VPC in the NL-AMS-2 region. The incident occurred between 09:07 UTC and 14:32 UTC. The issue has been resolved.

We currently have a switch down for this rack. Servers on this rack are unreachable. We are investigating on the root cause.

Our team is actively working on the situation. A potential fix is under testing and will be deployed if confirmed.

We're currently investigating an issue preventing some users from switching organizations, following their migration from Guest to Member. The issue affects a limited number of users who belong to multiple organizations. In many cases, clearing browser cookies resolves the issue.

The issue has been identified and a fix is being implemented.

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.

We are currently experiencing an outage affecting DEDIBOX servers in the fr-par-1 region. This issue may result in connectivity problems or unavailability of services hosted on the impacted servers.

We are currently investigating this issue.

BookMyName.com website and API were not available from 6:30 PM to 8:15 PM This incident impacted domain registration and administration on the Scaleway console.

We are currently investigating this issue.

Started at 8pm yesterday, 9 servers are impacted and an intervention is in progress.

An unexpected server failure occurred on san-ssd-3.rpn.online.net, causing the loss of the master node in the cluster. As a result, the RPN-SAN storage service became unavailable. Storage team is actively investigating the root cause and working to restore service as quickly as possible.

Our engineers noticed that the billing for our Apple Silicon products is not up to date. It will be retro-actively resumed 7/16/2025.

Issues on fr-par-2 impacting multiple products. Our team is actively working on it.

A small subset of customers have an interruption of logs and metrics coming from Scaleway products since the 13th of June. Custom Data Sources are not affected.

The following OS cannot be installed on Dedibox : archlinux, esxi and windows.

We have detected a switch down Servers in that rack currently have no public network access and are unreachable. Issue has been forwarded to our team for resolution.

The RPN switch is currently unreachable, resulting in a loss of RPN connectivity in rack H7. The public network remains operational.

We are currently experiencing a network incident in DC5 due to a switch failure. This is impacting a subset of Dedibox servers, which may face intermittent or total loss of network connectivity. Our teams are actively working to restore full service as quickly as possible.

We are currently investigating this issue.

The switch has rebooted several times, same thing for some servers.

We are currently experiencing a network incident in DC3 due to a switch failure. This is impacting a subset of Dedibox servers, which may face intermittent or total loss of network connectivity. Our teams are actively working to restore full service as quickly as possible.

We are experiencing a temporary issue affecting some dedicated server. Team has been warned.

Since 6th July 2025, 8:45 PM, Gemma 3 is currently experimenting slow response times and Llama 3.3 experienced a few short disruptions

We experienced a temporary issue affecting a limited number of servers at DC2. This was due to an internal operation in the datacenter. As a result, some servers may have become unavailable during the incident. All impacted servers are currently being restored. A full recovery is in progress.

Between July 3rd 2:00 PM UTC and July 4th 11:00 AM UTC, customers may have experienced high latencies on Object Storage in the NL-AMS region. This was due to an internal rebuild process. To limit the impact, operations were slowed down during the event. The situation has now stabilized and we are currently monitoring the service closely.

Our teams are currently investigating an issue affecting the container registry service in the AMS region. This issue may prevent users from pulling or pushing container images, impacting the deployment and operation of containerized applications. We apologize for any inconvenience caused and will provide updates as soon as more information is available.

Since 30th June 2025, 11:30am, we are experiencing periodic instabilities on the Mistral Small 3.1 inference engine. This may result in short, intermittent service disruptions for affected users. Investigations are ongoing to find and fix the root cause.

We continue to monitor the situation closely for any further issues.

The error rate is below the nominal threshold; we are continuing to monitor closely.

Due to elevated temperatures in France, some of our services are currently experiencing degraded performance. Our teams are actively implementing mitigation measures and closely monitoring the situation to prevent further impact.

We continue to monitor the situation closely for any further issues.

To prevent further issues, we will preemptively shut down several services in the datacenter. This may result in temporary downtime for your service. We are doing our best to recover the situation as quickly as possible.

Due to elevated temperatures in Netherlands, some of our services are currently experiencing degraded performance. Our teams are actively implementing mitigation measures and closely monitoring the situation to prevent further impact.

Due to elevated temperatures in Netherlands, some of our services are currently experiencing degraded performance. Our teams are actively implementing mitigation measures and closely monitoring the situation to prevent further impact.

Due to abnormal temperature, the Amsterdam Object Storage cluster is experiencing degraded performances. This may result in slower data access and upload/download operations. Our team is actively working to mitigate the issue and prevent further impact.

A network switch in DC5 room 1 rack C62 has experienced a failure. Dedibox servers in this rack have lost their RPN connectivity. Our technical team is actively working to resolve the issue and restore full connectivity.

Due to current temperatures, a subset of our cluster has restarted, inducing a temporary raise of our error rate (http 500 errors) above 0.1%. We are currently mitigating the issue and monitoring to avoid more troubles

The secondary DNS server 62.210.16.8/nssec.online.net is down. We are working to resolve that issue as quick as possible.

A fix has been implemented and we are monitoring the results.

The legacy DNS resolver 62.210.16.6, used on Dedibox installations before the introduction of new IP addresses, is currently experiencing connectivity issues. This may affect the resolution of DNS queries for impacted Dedibox instances.

The IP 51.159.208.135 is blacklisted by Microsoft. We are currently working on it.

The file system on a worker server hosting temporal data is full, causing all backups to fail and logs to not be handled properly. This may result in data loss and potential disruptions in service.

Network redundancy loss due to an equipment failure. All services are still running, but some customer may be impacted by a network redundancy loss. We are currently working on the matter.

There is currently a connectivity issue affecting the Virtual Private Cloud (VPCL) in the Amsterdam region (nl-ams-3). This issue is causing degradation in DHCP services and DNS resolution. Impact : Users may experience difficulties in obtaining IP addresses via DHCP. DNS resolution may be unavailable, affecting the ability to resolve domain names to IP addresses. This also impacts the connectivity of instances and Elastic Metal.

This incident has been resolved.

S3 checksum error in some client/sdk, we alway return the full object checksum even when the request is ranged, causing issue in some high-level wrappers that try to compare the range's checksum with the full object one. Full integrity of the objects aren't impacted, and all computed checksum are valid.

We are currently experiencing issues with MongoDB deployments in the fr-par region, which are ending in error. This may result in delays or failures when attempting to create new MongoDB instances. Our technical team is actively investigating the issue to restore normal service as soon as possible.

We have analyzed an issue to access the autoritative DNS of Linode (at least ns1/2/3/4/5.linode.com) to resolve some domain names (FQDN) from our network. You may use other DNS resolvers to solve this issue in the meantime than the ones provided with Scaleway and Dedibox if you have issue to resolve some FQDN behind Linode DNS autoritative servers (an example with Unbound and a public DNS like Google : 'unbound-control forward_add alpinelinux.org x.x.x.x'). We are not the sole provider to experience such issue, many other DNS public resolvers we have tested are experiencing the same anomalous behavior.

We've identified an issue where the quotas returned are not always accurate, which can cause the console to display an incorrect maximum value. As a result, certain actions might be limited in the console, even though the actual quotas are higher. Please note that this issue does not affect actions performed via API, CLI, or Terraform. Only the web console is impacted.

s1-a12-2.rpn.dc5 since 15:03 The RPN connection is not available for the servers connected to the switch.

Switch h6-6b54-2.ams1 is down, all the servers on it are unreachable. We're currently working on it.

We are currently investigating this issue.

We are currently investigating this issue.

Due to exceptional circumstances, the response time is slowed down. Sorry for the inconvenience

Since 13:29 (CET), no files or emails were stored and access to webmail was inaccessible.

The issue has been identified at around 3pm (CET). We are currently investigating it.

We have detected a switch down in Hall 2 E-E, Baie : E30. Servers in that rack currently have no public network access and are unreachable since 18/06/2025 05h30. The issue has been forwarded to our team for resolution.

We have detected a switch down in room 101-k31-2. Servers in that rack currently have no public network access and are unreachable. =================== 17/06/25 09H00 UTC Issue has been forwarded to our team for resolution.

Increasing number of 502 error. Our team is working to solve this problem.

We are currently being targeted by a phishing campaign. We invite you to be careful and check the invoices directly on your console. Our Trust and Safety team is working to resolve this.

We are currently investigating this issue.

This incident has been resolved.

Following a deployment of api-compute, we notice an elevated rate of 500 errors, mainly on fr-par-2, endpoints POST /ips and POST /servers.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

[fr-par-2] From 6:04 UTC to 7:28 UTC, customers could experience DHCP & DNS & NTP loss through VPC when using VPC's managed service. The situation is now resolved.

Issue started at around 8:14 CEST Some clusters unreachable via their LB

We are continuing to investigate this issue.

We have detected a switch down in DC5 room 1 1 rack D27 Servers in that rack currently have no public network access and are unreachable. An intervention is planned and a technician will carry out all the necessary checks.

We have detected a switch down in DC5 room 7 rack C57 bloc A Servers in that rack currently have no public network access and are unreachable. =================== Since 08.06.25 at 18h00. Issue has been forwarded to our team for resolution.

Since 2025-06-07 09:20 UTC, around half of the users cannot call their functions/containers endpoints in pl-waw region. Users are experiencing "connect: connection refused" or "Could not connect to server" errors. At first glance, this seems caused by a LB failure. We apologize for any inconvenience. We are on it.

Public switches in racks C7/C8/C9 went down at 5:34PM CEST Everything went back at 5:42PM CEST

13 buckets on the whole PL-WAW region have been impacted. We will contact the specific customers with a message coming soon from our support."

On Friday 28th of May at 09.00AM UTC, we did a scheduled operation. Since this operation, a small subset of buckets may suffer from a bad behavior that our technical team is currently investigating.

On June 2nd, a bug in our Payment API caused SEPA payment failures for some DDX2LT clients. As a fallback, the system tried to charge by credit card, but some of those payments also failed.We have identified the issue and are working on a fix. Once resolved, we will provide appropriate solutions for affected clients.

13 buckets on the whole PL-WAW region have been impacted. We will contact the specific customers with a message coming soon from our support."

On Friday 28th of May at 09.00AM UTC, we did a scheduled operation. Since this operation, a small subset of buckets may suffer from a bad behavior that our technical team is currently investigating.

On June 2nd, a bug in our Payment API caused SEPA payment failures for some DDX2LT clients. As a fallback, the system tried to charge by credit card, but some of those payments also failed. We have identified the issue and are working on a fix. Once resolved, we will provide appropriate solutions for affected clients.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Server: cPanel platforms 1004, 1005, 1006, 1007, 1010, 1011Maintenance: Server updateA downtime of 10 min can be expected on each platform during the maintenance

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently experiencing a technical issue with the installation of Ubuntu 24.04 LTS, our teams are currently working on it, we will keep you informed.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently experiencing a technical issue with the installation of Ubuntu 20.04, our teams are currently working on it, we will keep you informed.

This incident has been resolved.

A fix is being rolled out we are monitoring

We are continuing to investigate this issue.

Starting this morning around 11:35 CEST migrated volumes can't get detached anymore

This incident has been resolved.

A fix is being rolled out we are monitoring

We are continuing to investigate this issue.

Starting this morning around 11:35 CEST migrated volumes can't get detached anymore

A fix has been implemented and we are monitoring the results.

We are aware of issues affecting customers of the gemma-3-27b-it model since 15:00. We are currently investigating theses issues.

This incident has been resolved.

Our team has set up a fix and recovery work is now under the supervision of our engineers.

Several classic webhosting customers may experiencing 500/error SSL certificate errors.Our team is already working on it.

We will be undergoing scheduled maintenance during this time.

From June 3rd until June 12th, we are migrating b_ssd volumes, b_ssd snapshot, b_ssd snapshots and unified snapshots to Scaleway Block Storage (SBS). If your organization is affected, you have received a communication via email including the list of impacted resources. No action is required on your part, volumes will remain available during the migration window.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

This incident has been resolved.

Our team has set up a fix and recovery work is now under the supervision of our engineers.

Several classic webhosting customers may experiencing 500/error SSL certificate errors. Our team is already working on it.

This incident has been resolved.

The dashboard are no longer reachable on fr-par.

This incident has been resolved.

The dashboard are no longer reachable on fr-par.

We are investigating a problem that generated RPNv2 connectivity issue between our datacenters this morning around 07:52 UTC

We are investigating a problem that generated RPNv2 connectivity issue between our datacenters this morning around 07:52 UTC

A faulty link on a router generated packet loss and connectivity issues on the RPN network in DC3 room 4-6 between Friday May 30th and Monday June 02nd. This is now resolved.

This incident has been resolved.

Due to circumstances beyond our control, support will be exceptionally unavailable from 6 PM tonight until 10 PM.We apologize for this inconvenience.

This incident has been resolved.

Due to circumstances beyond our control, support will be exceptionally unavailable from 6 PM tonight until 10 PM. We apologize for this inconvenience.

This incident has been resolved.

Due to circumstances beyond our control, support will be exceptionally unavailable from 6 PM tonight until 10 PM.We apologize for this inconvenience.

This incident has been resolved.

Due to circumstances beyond our control, support will be exceptionally unavailable from 6 PM tonight until 10 PM. We apologize for this inconvenience.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

VPS management page and several endpoints are returning a 504 Gateway Time-out error. Our engineers are doing everything they can to resolve this quickly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

VPS management page and several endpoints are returning a 504 Gateway Time-out error. Our engineers are doing everything they can to resolve this quickly.

The root cause has been identified. A limit was reached, preventing new domain challenges to be created since 2025-05-26 06:42 UTC, thus leading to errors for new domains creation. This affected only a small part of the fr-par infrastructure (~20% of users).We are going to fix the limit, and add monitoring, so it doesn't happen again.Sorry again, and thanks for your understanding

The issue has been fixed. We have not found the root cause yet, but it's still under investigation. However, users should be able to create new custom domains.Sorry again for any inconvenience.

A bug prevents users to create new custom domains on their functions/containers. It affects around 20% of the clients in fr-par. For these users, custom domains end up in error after around 3 minutes, even if CNAME configuration is correct. Already created custom domains are not affected.We are on it. Sorry about the inconvenience.

This incident has been resolved.

We are currently investigating this issue.

The root cause has been identified. A limit was reached, preventing new domain challenges to be created since 2025-05-26 06:42 UTC, thus leading to errors for new domains creation. This affected only a small part of the fr-par infrastructure (~20% of users). We are going to fix the limit, and add monitoring, so it doesn't happen again. Sorry again, and thanks for your understanding

The issue has been fixed. We have not found the root cause yet, but it's still under investigation. However, users should be able to create new custom domains. Sorry again for any inconvenience.

A bug prevents users to create new custom domains on their functions/containers. It affects around 20% of the clients in fr-par. For these users, custom domains end up in error after around 3 minutes, even if CNAME configuration is correct. Already created custom domains are not affected. We are on it. Sorry about the inconvenience.

This incident has been resolved.

We are currently investigating this issue.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will migrate Kubernetes clusters to a network VPC to enable stricter isolation.Check our documentation for more informationhttps://www.scaleway.com/en/docs/kubernetes/how-to/manage-allowed-ips/No downtime or service impact is expected.Note: This upgrade will not apply to clusters using legacy private gateways. These clusters will continue to operate without changes.Here the schedule for each region : WAR: 19/05 - 20/05AMS: 21/05 - 23/05PAR: 26/05 - 30/05

This incident has been resolved.

Phone validation isn't possible on the Scaleway console due to a technical issue.Our team is currently investigate this issue.

This incident has been resolved.

Customers can not access Grafana.

This incident has been resolved.

Phone validation isn't possible on the Scaleway console due to a technical issue. Our team is currently investigate this issue.

This incident has been resolved.

Customers can not access Grafana.

A faulty link on a router generated packet loss and connectivity issues on the RPN network in DC3 room 4-6 between Friday May 30th and Monday June 02nd.This is now resolved.

A fix has been implemented and we are monitoring the results.

We are currently experiencing a technical issue with the installation of Ubuntu 20.04, our teams are currently working on it, we will keep you informed.

A fix has been implemented and we are monitoring the results.

We are currently experiencing a technical issue with the installation of Ubuntu 24.04 LTS, our teams are currently working on it, we will keep you informed.

This incident has been resolved.

Since 9:47:08 UTC users may experience errors when trying to connect to their Grafana or manage their Grafana Users.Ingestion / Alerting is not impactedIncident is no longer live since 13:35 UTCSituation under investigation

We are currently investigating this issue.

This incident has been resolved.

Since 9:47:08 UTC users may experience errors when trying to connect to their Grafana or manage their Grafana Users. Ingestion / Alerting is not impacted Incident is no longer live since 13:35 UTC Situation under investigation

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

An issue regarding VPS servers management is currently preventing customers from managing their instances. Deployed servers are unaffected.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

An issue regarding VPS servers management is currently preventing customers from managing their instances. Deployed servers are unaffected.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented since 7:15UTC / 9:15 CET and the service has been reestablished. We are monitoring the results.

We are implementing a fix.

Our Secret Manager product is currently out of service in the fr-par region since 05h18 UTC. the ‘CreateSecretVersion’ and ‘AccessSecretVersion’ methods are unusable.We apologize for the inconvenience and our engineers are working hard to resolve this quickly.

This incident has been resolved.

A fix has been implemented since 7:15UTC / 9:15 CET and the service has been reestablished. We are monitoring the results.

We are implementing a fix

Our KeyManager product is currently out of service in the fr-par region since 05h18 UTC.We apologize for the inconvenience and our engineers are working hard to resolve this quickly.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented since 7:15UTC / 9:15 CET and the service has been reestablished. We are monitoring the results.

We are implementing a fix

Our KeyManager product is currently out of service in the fr-par region since 05h18 UTC. We apologize for the inconvenience and our engineers are working hard to resolve this quickly.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented since 7:15UTC / 9:15 CET and the service has been reestablished. We are monitoring the results.

We are implementing a fix.

Our Secret Manager product is currently out of service in the fr-par region since 05h18 UTC. the ‘CreateSecretVersion’ and ‘AccessSecretVersion’ methods are unusable. We apologize for the inconvenience and our engineers are working hard to resolve this quickly.

The IP 51.159.208.135 of our Webhosting platform is blacklisted by Microsoft.We are currently working on it.

The IP 51.159.208.135 of our Webhosting platform is blacklisted by Microsoft. We are currently working on it.

The issue appeared at 3pm, after a new release. We rollbacked to the latest stable state and we will be merging a fix for what happened as soon as possible.

Due to internal technical updates, the Organization Settings and Support Tickets pages are currently unavailable. We appreciate your patience and understanding as we work to restore access as soon as possible.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be performing necessary upgrades on Cockpit databases to improve future performance and reliability on 19/05/2025.During the maintenance window, you may experience short latencies when accessing dashboards. We recommend you do not create new dashboards or edit existing ones during that window to avoid side effects. No impact is expected on all other actions.We apologize for any inconvenience this may cause and appreciate your understanding. We'll keep you informed as the maintenance progresses.

The issue appeared at 3pm, after a new release. We rollbacked to the latest stable state and we will be merging a fix for what happened as soon as possible.

Due to internal technical updates, the Organization Settings and Support Tickets pages are currently unavailable. We appreciate your patience and understanding as we work to restore access as soon as possible.

This incident has been resolved.

All the servers are back up and running on block M.Our engineers are continuing their investigations on block N.Thank you for your patience and understanding.

We have detected a switch down in DC2 room S101 G22 bloc N.Servers in that rack currently have no network access and are unreachable.===================25.05.25 05h32 UTCIssue has been forwarded to our team for resolution.

This incident has been resolved.

The servers are starting to recover on this switch.Thank you for your patience.

We have detected a switch down in AMS rack EE22 room hall2.Servers in that rack currently have no network access and are unreachable.===================24.05.25 12.13 UTCIssue has been forwarded to our team for resolution.

This incident has been resolved.

All the servers are back up and running on block M. Our engineers are continuing their investigations on block N. Thank you for your patience and understanding.

We have detected a switch down in DC2 room S101 G22 bloc N. Servers in that rack currently have no <public/private> network access and are unreachable. =================== 25.05.25 05h32 UTC Issue has been forwarded to our team for resolution.

This incident has been resolved.

The servers are starting to recover on this switch. Thank you for your patience.

We have detected a switch down in AMS rack EE22 room hall2. Servers in that rack currently have no <public/private> network access and are unreachable. =================== 24.05.25 12.13 UTC Issue has been forwarded to our team for resolution.

We have detected a switch down in DC5 room S1 Rack C34.Servers in that rack currently have no network access and are unreachable.===================26.05.25 09h41 UTCIssue has been forwarded to our team for resolution.

We have detected a switch down in DC5 room S1 Rack C34. Servers in that rack currently have no <public/private> network access and are unreachable. =================== 26.05.25 09h41 UTC Issue has been forwarded to our team for resolution.

This incident has been resolved.

We are continuing to work on a fix for this issue.

We are currently experiencing slowdowns in certain operations to thedomain name registries.All operations are automatically restarted by our teams, so you don't have to take any action yourself.The problem has been potentially identified, and a patch is currently being studied to restore normal operation.We are continuing our analysis and will update this page as soon as new information becomes available.

This incident has been resolved.

We are continuing to work on a fix for this issue.

We are currently experiencing slowdowns in certain operations to the domain name registries. All operations are automatically restarted by our teams, so you don't have to take any action yourself. The problem has been potentially identified, and a patch is currently being studied to restore normal operation. We are continuing our analysis and will update this page as soon as new information becomes available.

This incident has been resolved.

In all new projects created after 19/05/2025 3:30 PM, Datasources may not be properly synchronized in Grafana and hence may not be visualised. Data ingestion and query is not affected.A fix is under deployment.

This incident has been resolved.

In all new projects created after 19/05/2025 3:30 PM, Datasources may not be properly synchronized in Grafana and hence may not be visualised. Data ingestion and query is not affected. A fix is under deployment.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have detected a switch down in room 4-5 s45-d9.dc3, s45-d10-dc3.Servers in that rack currently have no public network access and are unreachable.12.05.25 00h37 CESTIssue has been forwarded to our team for resolution.

This incident has been resolved.

As of 2025/05/04 13:00 CEST, the service degradation affecting the container registry has been resolved. The registry has since been operating normally, and our team will continue to monitor it to ensure ongoing stability.

Registry is unusually slow, with a lot of latencies and instabilities, causing trouble to other services such as serverless container and function too.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have detected a switch down in room 203-B rack J5Servers in that rack currently have no public network access and are unreachable.Network team is currently investigating the issue.

A fix has been implemented and we are monitoring the results.

We are aware of issues affecting customers of the gemma-3-27b-it model since 15:00. We are currently investigating theses issues.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

No more sign up possible due to captcha error. We are currently investigating

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have detected a switch down in room 4-5 s45-d9.dc3, s45-d10-dc3. Servers in that rack currently have no public network access and are unreachable. 12.05.25 00h37 CEST Issue has been forwarded to our team for resolution.

This incident has been resolved.

As of 2025/05/04 13:00 CEST, the service degradation affecting the container registry has been resolved. The registry has since been operating normally, and our team will continue to monitor it to ensure ongoing stability.

Registry is unusually slow, with a lot of latencies and instabilities, causing trouble to other services such as serverless container and function too.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have detected a switch down in room 203-B rack J5 Servers in that rack currently have no public network access and are unreachable. Network team is currently investigating the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

No more sign up possible due to captcha error. We are currently investigating

Swith has been replaced per a new one and all the customer servers seems back for the business.

We have detected that public switch was down in DC2 Room 101 Rack A20.Servers in that rack currently have no network access and are unreachable.

Swith has been replaced per a new one and all the customer servers seems back for the business.

We have detected that public switch was down in DC2 Room 101 Rack A20. Servers in that rack currently have no network access and are unreachable.

This incident has been resolved.

We are continuing to work on a fix for this issue.

We have detected a switch down in DC2 Room 101 - s101-g27-13.dc2 Servers in that rack currently have no public network access and are unreachable. =================== Since 17.05.25 01h53 UTC. Issue has been forwarded to our team for resolution.

The incident has been resolved

The fix has been deployed and we are monitoring the results.

The issue has been identified and a fix has been prepared, it will be deployed as soon as possible

RPN service was unreachable during 11 minutes for the associated servers. Start time : 2025-05-16 16:15 CEST End time : 2025-05-16 16:26 CEST

This incident has been resolved.

All products above VPC and Instance have been recovered since 10.30 AM UTC. A public postmortem will be available as soon as possible.

Most of impacted products (Instance, Kapsule, LbaaS, Serverless) have recovered since 10:10 UTC, some Load Balancers are still being fixed, our technical team is working on it.

We are continuing to investigate this issue.

Fully resolved on VPC network side, some products are still impacted.

We are continuing to investigate this issue.

We encountered an issue with our VPC product. A network outage happened between 09:24 UTC to 09:29 UTC in FR-PAR-1. During this time-frame VPC related services might have been impacted. These related services are Instances, Kubernetes, Load Balancer, Databases, Network, Serverless Jobs. The root cause has been found.

This incident has been resolved.

Partial VPC DNS loss from 14:33 UTC to 14:36 UTC and from 15:18 UTC to 15:28 UTC. Customers can experience high DNS failures from within VPC during those two timeframes. We are investigating on the root cause. Everything is back to normal.

This incident has been resolved.

Since 1:08AM UTC Generative APIs encounter disruption of service. We are actively investigating the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Since around 3:15PM UTC, secret versions cannot be created in the FR-PAR Secret Manager. We are investigating the issue.

EM unreachable from 2025-05-16 05:07 UTC to 05:11 UTC (4 minutes). The associated network device rebooted unexpectedly.

This incident has been resolved.

PSU issues on rack h22 block F and block N. Some servers may be unreachable. Replacement are in progress.

RPN service is down on Rack H22 block F.

DC2 rack H22 block N, block F unreachable since 11:25 CEST. Analysis in progress.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have detected a switch down in Room 4-3 : s43-d20.rpn.dc3. Servers in that rack currently have no <public/private> network access and are unreachable. 11.05.25 00h57 UTC Issue has been forwarded to our team for resolution.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We have detected a switch down in room 101 - s101-g27-13. Servers in that rack currently have no public network access and are unreachable. 11.05.25 05h22 UTC Issue has been forwarded to our team for resolution.

The root cause was due to the VPC incident we encountered this morning. https://status.scaleway.com/incidents/nygwhbpk0sd4 During this time you may have encountered instability on your Redis clusters. Everything is back to normal. If you are still encountering an issue please open a ticket to our support team.

A fix has been implemented and we are monitoring the results.

Auto-healing workflows based on monitoring are triggered and rebooted some clusters.

This incident has been resolved.

Due to the migration of BookMyName, ordering Web Hosting is currently not possible on Elements. Thank you for your understanding.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The pf14-mysql is up and in monitoring.

The pf14-mysql & pf15-mysql have been out of service since 8h15 AM. Our engineers are doing their utmost to restore the service as soon as possible.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The pf17-mysql have been out of service. Our engineers are doing their utmost to restore the service as soon as possible.

S3 checksum error in some client/sdk, we alway return the full object checksum even when the request is ranged, causing issue in some high-level wrappers that try to compare the range's checksum with the full object one.Full integrity of the objects aren't impacted, and all computed checksum are valid.