Scaleway

Affected: Generative API

1. investigating 2026-10-21 18:05 UTC

   Since 7 pm, dedicated deployment deletion has been failing. Re-creation after deletion will remain impossible until the incident is resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Instances, VPC

1. identified 2026-10-21 16:31 UTC

   Since 16:00 UTC, Instances APIs are unavailable on it-mil-1. This also has some minor impacts on the region: unable to delete a VPC or a project.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Hosting, Web Hosting

1. identified 2026-10-21 14:38 UTC

   The PHP project released today a fix for two critical vulnerabilities allowing unauthenticated remote code execution (CVE-2026-109618, CVE-2026-109619, CVSS 9.2 — no complete mitigation exists): https://www.php.net/archive/2026.php#2026-10-21-5 As a precaution, we have taken...

2. identified 2026-10-22 06:20 UTC

   [Update] Security Maintenance – Web Hosting Services Security patching for the php2shell vulnerability is progressing: cPanel Environments (Resolved): PHP versions have been updated across all Scaleway and Online.net cPanel servers (as well as Scaleway Plesk). Maintenance mode...

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Dedibox, Dedibox Console

1. investigating 2026-10-21 14:37 UTC

   Emergency Maintenance in Progress As part of our investigation into the PHP2SHELL vulnerability (CVE), we are placing console.online.net and api.online.net into maintenance mode as a precautionary measure. The entire console is temporarily unavailable. This maintenance affects...

2. investigating 2026-10-21 21:35 UTC

   Investigation and mitigation of the PHP2Shell vulnerability are still ongoing. Your data and dedibox servers remain safe. You can continue to manage Dedibox servers through the Scaleway Console. We will restore the normal service status once maintenance is complete.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: BookMyName

1. investigating 2026-10-21 14:06 UTC

   Started: 21 Oct 2026, 15:50 CEST Status: Emergency maintenance in progress Impact: All BMN services are unavailable. The PHP project released today a fix for two critical vulnerabilities allowing unauthenticated remote code execution (CVE-2026-109618, CVE-2026-109619, CVSS 9.2 —...

2. identified 2026-10-21 16:51 UTC

   Update at 18:40 CEST The BookMyName website, its webmail, and the RDAP services are back up. The redirection service is still down: it requires further investigation before it can be patched and restored.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-10-21 12:00 UTC

   An upgrade operation of the Block storage api on fr-par-2 generated a blocking transaction which impacted the control plane of this AZ The issue occurred from 12:23 to 12:28 UTC and generated a high rate of 500 errors. The problem was quickly fixed by the engineers of the...

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Generative API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. monitoring 2026-10-21 09:20 UTC

   New deployment creation is temporarily unavailable due to infrastructure capacity constraints. Existing deployments are unaffected. We've identified the situation.

2. identified 2026-10-21 09:24 UTC

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

3. resolved 2026-10-21 17:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-10-21 08:44 UTC

   * 2026-10-20 17:45 CEST : Partial unavailability of custom logs datasource * 2026-10-20 18:00 CEST : mitigation deployed, stabilizing availability progressively * 2026-10-21 05:00 CEST : automated event happened, which triggered partial unavailability again for part of our...

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: IAM

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-10-20 15:37 UTC

   Users signing in with SAML who had not yet configured MFA were unable to log in. The issue was caused by a recent frontend release. A fix has been implemented, and an updated version of the account app is being deployed.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: fr-par-1, fr-par-2, fr-par-3, nl-ams-1, nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3, it-mil-1, it-mil-2, it-mil-3, Generative API

1. investigating 2026-10-20 15:31 UTC

   Started Tuesday 20th October @ 5:04pm The glm-5.3 model is consistently returning timeout errors on all requests. We are working at fixing the issue.

2. monitoring 2026-10-20 15:42 UTC

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

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Object Storage

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. identified 2026-10-20 15:21 UTC

   Following an infrastructure deployment, connectivity was disrupted across several racks, potentially impacting Object Storage customers in the fr-par region through increased latency and request errors. The issue has been identified, and our engineering teams are currently...

2. identified 2026-10-20 15:27 UTC

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

3. monitoring 2026-10-20 15:48 UTC

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

4. monitoring 2026-10-20 16:13 UTC

   Object Storage services in the fr-par region have returned to normal operating conditions following the deployment of the fix. Our teams continue to closely monitor the infrastructure to ensure service stability before marking the incident as resolved.

5. resolved 2026-10-21 12:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Generative API

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-20 13:59 UTC

   Started Tuesday 20th October 2:50pm The model is not available. We're working to fix it asap.

2. resolved 2026-10-20 14:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: fr-par-1, fr-par-2, fr-par-3, nl-ams-1, nl-ams-2, nl-ams-3, pl-waw-1, Cockpit, pl-waw-2, pl-waw-3, it-mil-1, it-mil-2, it-mil-3

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-20 10:12 UTC

   After a faulty deployment, listing data exporters in the Cockpit Console results in error.

2. resolved 2026-10-21 07:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: APIs, it-mil-1, it-mil-2, it-mil-3

1. investigating 2026-10-20 09:23 UTC

   We are currently experiencing degraded performance with it-mil APIs. Some requests may see elevated latency, intermittent errors, or timeouts. Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible.

2. monitoring 2026-10-20 10:07 UTC

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

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Generative API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-10-19 17:02 UTC

   19th October from 2:30pm to 7pm Some requests to the deepseek-v4.1-flash model have experienced elevated timeouts. We have implemented a mitigation, and error rates are improving. We're monitoring the situation.

2. monitoring 2026-10-19 17:15 UTC

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

3. resolved 2026-10-20 13:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Serverless-Database

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-19 07:45 UTC

   Since Saturday October 18, 2026 at 07:55 UTC (09:55 Paris time), Serverless SQL Databases as occured slow cold start for the DB and DB in status error.

2. resolved 2026-10-19 09:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Dedibox

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-19 07:30 UTC

   PUB service down on devices located in PARDC3 / Room 4-4 / Rack C18 since 2026/10/18 12:30 UTC, Checks in progress

2. monitoring 2026-10-19 09:10 UTC

   A faulty device has been replaced.

3. resolved 2026-10-20 06:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Instances

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-10-19 07:27 UTC

   An issue on a network device generated instability between 2026/10/17 10:42 UTC and 2026/10/17 10:57 UTC for devices located in rack 6.12.32 room Hall6 in AMS1

2. identified 2026-10-19 07:28 UTC

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

3. resolved 2026-10-19 07:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: fr-par-1, Instances

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-16 17:22 UTC

   Servers in room 108 experience temperature increase. This lead to CPU throttling and may result into unreachable instance. We are working with our datacenter provider to fix the situation.

2. monitoring 2026-10-16 17:43 UTC

   Temperatures are decreasing following an intervention by our service provider.

3. resolved 2026-10-16 18:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Generative API

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-16 13:22 UTC

   Timeouts are observed on qwen3-embedding-8b model through the Generative API.

2. resolved 2026-10-16 13:52 UTC

   The incident is now resolved. Customers should not see timeouts anymore. We continue to monitor the related deployments.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Dedibox, DC3

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-15 08:17 UTC

   We are currently experiencing an issue with the public switch located in Rack S46-E16 at Opcore-DC3. The switch is currently unreachable, and the root cause of the issue is still under investigation. As a result, all customer servers connected to this switch are currently...

2. identified 2026-10-15 08:37 UTC

   We found the root cause and applied a patch in order to recover the service. However, while further incidents cannot be entirely ruled out, our technical teams are actively working to identify and implement the necessary measures to prevent recurrence.

3. resolved 2026-10-19 15:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Dedibox, DC2

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-15 06:03 UTC

   We have detected a public switch is down in DC2, Room : 205 205, Rack G2

2. resolved 2026-10-15 10:26 UTC

   1st network device replaced at : 10:38 2nd network device replaced at : 11:58 Issue was due to network device that broke due to a powersurge in the rack

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: DC5, RPN

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-13 10:46 UTC

   We have a temporary outage on a RPN Switch bay A53 an A54 which might cause traffic issue. As such, a maintenance is planned : 14/10 - 10 AM UTC/12 AM Paris time A short interruption (approximately 5 minutes) is to be expected.

2. resolved 2026-10-14 10:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Dedibox, DC5

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-12 16:46 UTC

   We are currently experiencing a network incident affecting a switch in DC5, which is currently unreachable. Our technical team is investigating the situation and working on the required recovery actions.

2. resolved 2026-10-13 12:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Domains

1. investigating 2026-10-11 10:10 UTC

   Several reports of inconsistencies in the zones between our DNS servers s0.dom.scw.cloud and s1.dom.scw.cloud

2. monitoring 2026-10-11 11:04 UTC

   Updates had piled up, causing these issues. It has now been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Excellence

1. identified 2026-10-08 16:35 UTC

   En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude. Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais. Nous vous...

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Excellence

1. identified 2026-10-08 16:27 UTC

   Due to a high volume of requests, it may be difficult to reach our teams by phone. If needed, we invite you to contact us directly by submitting a ticket so that your request can be processed as quickly as possible. Thank you for your understanding. En raison d’un nombre élevé...

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Jobs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-08 13:38 UTC

   [Started Around 14h00 CET] Jobs cannot be executed. Clients will see job runs stuck in transient states like validated, queued, or running. Issue is under investigation

2. resolved 2026-10-08 14:13 UTC

   The issue is resolved. The Jobs API v1alpha1 was not available during incident and clients may have experienced PermissionDenied errors. The Jobs API v1alpha2 was available but job runs were stuck in transient states (validated, queued or running) after start. The Jobs are being...

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Dedibox VPS

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-08 11:48 UTC

   Customers may be unable to connect to their Dedibox VPS in the Paris location due to a locked state.

2. resolved 2026-10-08 13:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: fr-par-1, fr-par-2, fr-par-3, Container Registry, Jobs, Kafka, Serverless Container, Serverless Functions, Clusters for Apache Spark™

1. investigating 2026-10-08 08:27 UTC

   We are currently observing an increased rate of 5xx errors on the container registry in the fr-par region. Some image push and pull operations may fail or experience delays. Our teams are actively investigating, and we will provide an update as soon as more information is...

2. investigating 2026-10-08 08:29 UTC

   We are continuing to investigate this issue.

3. investigating 2026-10-08 08:54 UTC

   We added other impacted products and we are still investigating.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Cockpit

Failure mode: The text does not say enough to tell. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-07 15:13 UTC

   During 15 minutes, we have some troubles to ingest logs & metrics from products on IT-MIL. This was due to a maintenance operation not compatible with the last extension to MIL2/MIL3.

2. resolved 2026-10-07 15:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Secret Manager

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-07 13:24 UTC

   key manager api unavailable following database migration

2. identified 2026-10-07 13:52 UTC

   incident has been mitigated, we are implementing a long-term solution

3. resolved 2026-10-09 13:00 UTC

   This incident has been resolved!

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Generative API

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-06 15:02 UTC

   [15h00 utc+2] We are experiencing instabilities with a critical part of the glm-5.2 model infrastructure, working actively on the mitigation

2. resolved 2026-10-09 10:13 UTC

   The incident is now resolved, the situation is back to nomal.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Domains

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-06 14:17 UTC

   [11:21:22] BookMyName api logs shows no calls coming from online api

2. resolved 2026-10-06 14:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Network

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-06 10:57 UTC

   Since 11h30, Public Switch in rack b11 room 1 is down causing connectivity issues for some services, Our team is investigating.

2. resolved 2026-10-06 14:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Excellence

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. identified 2026-10-06 10:01 UTC

   Due to a high volume of requests, it may be difficult to reach our teams by phone. If needed, we invite you to contact us directly by submitting a ticket so that your request can be processed as quickly as possible. Thank you for your understanding. En raison d’un nombre élevé...

2. resolved 2026-10-08 08:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Dedibox, DC5

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-06 09:12 UTC

   Following an electrical maintenance, there are several servers down and at least 3 switchs down in row D.

2. monitoring 2026-10-06 10:54 UTC

   The maintenance is complete, and we are currently monitoring the results.

3. resolved 2026-10-07 12:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Hosting

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-05 15:17 UTC

   There is currently an access issue on the 1004 platform. We are currently investigating the matter.

2. resolved 2026-10-05 16:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Dedibox VPS

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-05 07:52 UTC

   Customers may be unable to connect to their Dedibox VPS in the Paris location due to a locked state.

2. resolved 2026-10-05 18:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Jobs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-02 10:11 UTC

   Customers can't execute jobs. Job runs will be stuck in validated status.

2. monitoring 2026-10-02 11:44 UTC

   Job runs can now be executed.

3. resolved 2026-10-02 15:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Transactional Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-09-30 19:47 UTC

   The IP address 51.159.124.109 has been blacklisted by Spamhaus.

2. resolved 2026-09-30 19:59 UTC

   The incident has been resolved and the IP is no longer blacklisted.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Billing, Environmental Footprint, IAM, Load Balancer

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-30 09:35 UTC

   Account API is down. Console may be unusable

2. investigating 2026-09-30 09:41 UTC

   We are continuing to investigate this issue.

3. identified 2026-09-30 09:42 UTC

   Services have recovered, we are investigating, but there should not be any user facing impacts anymore.

4. resolved 2026-09-30 14:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: fr-par-1, fr-par-2, fr-par-3, Serverless-Database

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A human mistake during operations. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-09-30 09:10 UTC

   [03:00]: Following the temporal migration of yesterday, the daily backups of Serverless SQL DB didn't work last night. Backups are expected to become available again later today.

2. resolved 2026-09-30 12:25 UTC

   Backup services have been restored and are now available.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: fr-par-1, fr-par-2, fr-par-3

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. monitoring 2026-09-29 13:44 UTC

   We have observed local perturbations on the backbone network of FR-PAR region, fixes have been deployed, we are monitoring the situation

2. resolved 2026-10-06 08:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: fr-par-1, fr-par-2, APIs, fr-par-3

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-29 08:29 UTC

   Instabilities when contacting Scaleway APIs

2. resolved 2026-09-29 08:48 UTC

   A network offload of traffic caused some transient issues, the offload was stopped in order to recover all services.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: AMS, RPN

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-29 07:41 UTC

   The rpn device inside the rack 6.12.71 in Amsterdam is currently unreachable. At this time, the root cause has not yet been identified. Our Network team is investigating the issue and will provide further updates as soon as more information becomes available.

2. investigating 2026-09-29 07:49 UTC

   We are continuing to investigate this issue.

3. resolved 2026-09-29 11:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Cockpit

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-28 09:46 UTC

   Some users report errors in custom metrics ingestion since 2026-09-16 We are investigating to find out the scope of the incident.

2. identified 2026-09-28 09:46 UTC

   Incident is resolved, we are still monitoring to make sure that everything runs smoothly

3. resolved 2026-10-07 12:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: pl-waw-1, pl-waw-2, pl-waw-3, Object Storage

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-28 08:49 UTC

   Since the 25/09 (last friday), the S3 pl-waw region is overloaded with operations. We're currently working to mitigate that.

2. monitoring 2026-09-28 13:41 UTC

   The issue has been identified, fixes have been deployed, we're back to the nominal state, monitoring.

3. resolved 2026-09-30 07:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: APIs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-26 18:25 UTC

   We are observing an unexpected increase in 5xx error rate. Investigations are underway.

2. resolved 2026-10-02 07:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Edge service

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-09-25 13:45 UTC

   Edge Services may return truncated HTTP content due to a faulty cache server. The incident is mitigated.

2. resolved 2026-09-28 13:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-24 08:39 UTC

   The latest version of rescue operator was not deployed to the nl-ams and fr-par regions following the latest changes to the already-deployed Provisioner. This caused installation issues for both Linux and ESXi operating systems.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Generative API

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-23 19:51 UTC

   [18:30] Qwen3 235b model performance is degraded, a few timeouts have been observed [21:30] Performance is still sub-optimal but timeouts are mostly gone

2. resolved 2026-10-02 07:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-22 14:57 UTC

   [10:34] During 3 minutes requests sent to the gpt-oss-120b could not be processed leading to 502 HTTP errors responses [10:37] Service back to normal. gpt-oss-120b able to process requests

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-19 22:30 UTC

   We have detected a switch down in DC2/S301/D13 Servers in that rack has lost private network access. =================== 2026/09/20 12:37 UTC The issue has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-18 14:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-22 07:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-17 07:59 UTC

   From Wednesday, September 16 at 18:00 CEST to Thursday, September 17 at 09:45 CEST, some of our components were unable to start after ingesting data. A small portion of customers may have missing data from this time period.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-16 13:52 UTC

   VMs with new subnet may have had issues with dns resolutions

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-16 07:57 UTC

   The issue has been resolved. If you are still experiencing issues, we invite you to create a support ticket.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-16 06:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-15 14:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-15 13:59 UTC

   All operations are impacted. Kafka already deployed is reachable.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-15 16:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-14 16:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Excellence

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. identified 2026-09-14 13:11 UTC

   Processing of current tickets may take longer than usual. Our teams are currently working to restore the service as soon as possible. Thank you for your understanding.

2. resolved 2026-10-07 10:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-21 09:27 UTC

   The platform is accessible again. Teams are in the process of verifying that the operation of the platform is compliant. We apologize for this interruption.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-14 09:09 UTC

   Public Gateway creation/update in fr-par-1 were stuck in a transient state.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-11 08:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-28 13:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-09 08:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-09 15:14 UTC

   A fix has been successfully deployed, and the incident is now resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-08 15:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-08 09:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-08 07:31 UTC

   At 03:45 AM CEST on 08/09/2026, the public switch located in AMS1 room H6 rack 6B52 has rebooted. During the reboot, all servers located in this rack have lost public connectivity, all services are now restored.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-08 08:05 UTC

   This incident has been resolved, the public switch is now reachable again.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-07 18:50 UTC

   We were unable to ingest some traces from 2026-09-01 22:00:00 to 2026-09-02 11:00:00 Incident is opened and closed retroactively

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-07 13:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-07 10:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-05 13:55 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-05 14:00 UTC

   Incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-04 10:02 UTC

   The main problem has been found and resolved. The email in queue may take some minutes to be completely sent.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-03 15:07 UTC

   From 11:30 AM to 3:30 PM, communication with the .CO TLD was unstable, causing errors in all domain‑related operations

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-07 09:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-02 15:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: pl-waw-3, VPC

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. monitoring 2026-09-02 13:44 UTC

   Between 09:00 UTC on September 1, 2026, and 13:30 UTC on September 2, 2026, some newly created infrastructure in the pl-waw-3 Availability Zone experienced temporary network connectivity issues. The issue has been fully resolved, and all services are now operating normally. No...

2. monitoring 2026-09-02 13:58 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-09-28 13:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-01 12:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-01 14:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: Dedibackup

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. identified 2026-08-30 10:06 UTC

   Since August 26th, the dedibackup on DC3 has been unreachable and is returning 500 errors.

2. resolved 2026-09-28 13:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-27 22:14 UTC

   The issue should now be fixed. We invite you to retry installing your Elastic Metal server if it is still in an error state.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-27 15:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-27 14:57 UTC

   Outage Timestamps : Start-Time : 13:47 UTC End-Time : 13:56 UTC Due to a production operation on a specific network device. Instances located on the hypervisors connected to this network device have been impacted by a network outage. This outage has impacted all outbound traffic...

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-27 15:38 UTC

   Loki is up on all Regions. Some logs have been lost because too old for replay, we're sorry for the impact.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-27 16:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-28 08:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-07 11:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-26 08:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-25 09:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-25 08:06 UTC

   As of 7:47 a.m. UTC, latencies have returned to a nominal state.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-21 13:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-21 09:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Affected: fr-par-1, fr-par-2, fr-par-3, VPC

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. monitoring 2026-08-20 16:06 UTC

   Following a configuration issue during a deployment, numerous routes stopped being advertised, which may have impacted routing to the PAR VPN gateways.

2. resolved 2026-09-28 13:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-19 13:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-18 13:26 UTC

   After investigation, we have found the root cause. The issue happened because of blackholed traffic, but only on some Private Networks with a specific configuration: - PNs with ACLs - PNs inside VPCs with "enable_routing" set to false Anyway, we have rolled back the component...

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-17 14:08 UTC

   Customers may have experienced connectivity issues affecting some instances in the PL-WAW-2 region, preventing access via VPC. The issue was caused by a misconfiguration applied to an internal component. A fix was applied, and connectivity has been restored.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-14 14:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-18 15:29 UTC

   We are pleased to inform you that the issue has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Security incident or emergency response to a vulnerability. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-13 16:05 UTC

   The ESET has removed the domain from their blacklist.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-14 08:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-18 15:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-07 18:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-18 15:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-06 17:11 UTC

   The servers have been put back into production and latencies are now nominal as of August 5, 6:30 PM CEST.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-07 12:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-07 12:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-06 08:33 UTC

   [05:00] Increase of query load broke store gateways.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-07 12:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-05 15:39 UTC

   Everything has been stable again since 18:28 UTC. yesterday. The incident is closed.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-04 17:04 UTC

   This incident has been resolved, and all servers should now be reachable.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-04 09:18 UTC

   Between approximately 15:00 and 15:45 CEST on 3 August, a Web Hosting platofrm pf-014 in fr-par experienced intermittent unavailability, resulting in HTTP errors and slow responses for websites hosted on it. Other servers in the Web Hosting fleet were unaffected. The cause was...

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-03 07:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-31 14:49 UTC

   At 15h55, public switch s45-d14.dc3 has rebooted; public network connectivity was affected for 10 minutes for all servers attached to it.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-29 23:28 UTC

   The Transactional Email services have been running without any issue for a few hours, and we were able to partially retrieve webhook events for the last 15 days. Webhooks sent from 2026-07-29 13:10:28.678436+02 to 2026-07-29 17:23:09 UTC are definitively lost. To prevent further...

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-29 14:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-29 09:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-28 17:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: A model or AI component. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-30 08:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-29 13:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-28 07:00 UTC

   July 28, 2026 — 09:02 CEST: Our monitoring system detected connectivity issues affecting multiple PRO2 hypervisors in FR-PAR-1. Several servers appeared unreachable.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-24 10:12 UTC

   The faulty switch has been replaced. Every server should now be reachable.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-30 08:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-23 15:23 UTC

   The situation has been back to normal since 3:15 PM. Pushes to the registry and container deployments in the IT-mil region are working again. Sorry about any inconvenience.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-23 14:34 UTC

   [14:45] While upgrade our infra some of the clusters were unreachable

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-22 12:57 UTC

   During compute instances incident on fr-par (cf. this status: https://status.scaleway.com/incidents/bsp2y5fysy9w), some jobs were interrupted during execution or were not executed at all. They ended in an Interrupted state with a reason technical_error. This happened...

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-22 09:55 UTC

   Incident is now resolved. Please read instructions in the previous message if your container or namespace has one of the following error messages. Sorry again for any inconvenience.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-22 04:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-22 04:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-21 19:50 UTC

   This incident has been resolved since 19:15 UTC.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-21 16:44 UTC

   The incident has been resolved and the situation is stable again since 16:30 UTC. Pushes to registry and containers deployment on the it-mil region are working again. Thank you for your patience on the matter.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-21 08:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-20 14:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-20 14:07 UTC

   The issue has been resolved by our product team. Pools should now be created without any further issues.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-22 01:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-17 13:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-20 09:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-17 08:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-16 12:33 UTC

   Due to NotReady node, we lost all ingestion on it-mil-1 for ~1h Start at 13h20 -> Ended at 14h20

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-16 06:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-17 07:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-15 17:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-12 10:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-10 14:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-10 09:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-10 10:45 UTC

   The connectivity issues affecting Serverless Containers in the nl‑ams region occurred between 07:40 CET and 09:30 CET. As of 09:30 CET, the service is stable and fully reachable. If you still experience any problems, please contact our Support team. Thank you for your patience.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-09 16:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-09 15:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-10 07:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-09 08:06 UTC

   Customers may experience a partial outage on public connectivity for a few minutes due to a reboot of the public switch s301-b5-2 in DC2.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-09 16:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-22 01:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-09 07:00 UTC

   Today, between 9:12 AM and 10:15 AM (Paris time), customers experienced a high number of HTTP 503 errors on Edge Services pipelines with Object Storage backends due to DNS resolution issues affecting an internal component. This incident has now been resolved, and our teams are...

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-08 21:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-08 16:33 UTC

   [~17h] Customers may experience a high amount of 503 errors on Edge Services pipelines with Object Storage backends due to DNS resolution issues on an internal component.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-08 16:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-09 06:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-08 10:20 UTC

   Customers may have experienced a partial outage of public connectivity on servers attached to the public switch h6-6b60-6.ams1 in the AMS1 region.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-08 16:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-08 10:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-10 13:32 UTC

   Newly restored instances will not be affected by this issue. Impacted customers will be contacted individually with updates regarding the corrective maintenance on their snapshots.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-07 09:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-07 05:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-07 09:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-06 15:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-06 09:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-06 09:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-04 21:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-09 13:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-02 10:30 UTC

   Customers may experience flaky behavior on the Environmental Impact Availability Report and Environmental Dashboard due to an internal dependency.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-03 07:47 UTC

   Customers may have experienced connectivity issues with their Dedibox VPS instances in the Paris region due to an internal infrastructure issue. The issue has been resolved and all services are now operating normally.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-02 07:57 UTC

   Customers may experience high latency on Block Storage volumes (only bssd) in the fr-par-2 region due to a slow response from an internal component.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-02 14:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-06 09:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-06-30 14:06 UTC

   Customers in DC3 may experience a short unavailability of RPN connectivity due to an RPN switch reboot.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-30 10:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-01 04:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-08 12:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-15 17:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-01 12:31 UTC

   The incident is fully solved since around 7h30 UTC on 2026-06-30. It was a side-effect of https://status.scaleway.com/incidents/0vtzpl5bklrh where cockpit metrics were lost on fr-par/pl-waw. There should have been no impact on your infrastructure.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-29 15:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: A model or AI component. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-09 13:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-06-26 13:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-08 12:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-06-25 17:53 UTC

   Since 10:30 UTC, customers may experience issues retrieving their product logs to Cockpit due to an internal dependency failure in the nl-ams region. Logs are not ingested anymore, so it seems logs are lost forever.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-01 09:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-06-25 09:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-06-25 10:05 UTC

   Servers have been moved to a different location and brought back online. All objects, including one-zone objects should be accessible.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-25 08:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-06-24 15:08 UTC

   Following a component overload in Cockpit during an upgrade designed to improve its resilience, difficulties integrating logs and metrics arose from Scaleway products between 11.30 am and 3.30 pm. There may have been a partial loss of this data.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-23 15:34 UTC

   The issue has been resolved and monitoring data is now being collected as expected.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-07-01 09:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-22 14:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-22 12:24 UTC

   Everything is back to normal. Services are up and running. If you are still encountering an issue, please contact our support team.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-21 04:30 UTC

   Today, from 04h48 to 04h50 UTC a block cluster hosting b_ssd volumes reported high latencies following a network issue affecting a server rack Cluster recovered at 04h51. Very few IO operations were still stuck until manual intervention at 05h10 UTC. Situation is normal since.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-20 21:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-07-09 15:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-22 08:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-18 12:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-18 11:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-22 08:34 UTC

   Observability volumes are increasing, and we are reaching some limits with serverless log ingestion. We have resized the cache for our ingestion components, and we plan to deploy smart features to this component this week.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-17 10:30 UTC

   Customers may experience connectivity issues with Edge Services due to a temporary outage of node servers.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-17 12:56 UTC

   After an extended period of monitoring, we have confirmed that all systems are stable and fully operational.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-07-01 09:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-16 17:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-17 12:26 UTC

   Customers may have experienced delays when creating new batches in Generative APIs due to an internal dependency issue. The issue has been resolved and all batches are now being processed normally.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-07-01 09:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-07-01 09:06 UTC

   A maintenance will be planned in July to replace the faulty device

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-15 17:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-15 15:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-15 13:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-15 10:20 UTC

   The root cause was due to a hardware issue on the switch. We will do a replacement in a near future. A separate maintenance will be created to prevent any further issue. All servers linked to this switch and racks are up and running.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-13 09:07 UTC

   Customers may experience connectivity issues with MySQL databases on pf-013 due to a storage capacity issue on an internal component.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-12 18:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-12 17:00 UTC

   The DNS servers ns0.online.net (IPv4) for Dedibox domains and ns0.dom.scw.cloud (IPv4) for Scaleway domains are unreachable, but the other DNS servers remain available.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-12 19:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-11 10:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-11 08:24 UTC

   Between 2026-02-10 09:00 UTC and 2026-02-11 08:00 UTC, around 50% of container logs were not forwarded to users' cockpit. After investigation, a faulty reload of our logs collector caused the issue. After reloading, some logs might have been backfilled, but not the entirety. The...

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-10 15:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-10 08:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-09 15:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-09 07:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-08 14:22 UTC

   Customers may experience connectivity issues in the it-mil-1 zone due to a DHCP service disruption.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-08 14:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-08 12:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-04 12:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-05 09:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-05 14:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-01 08:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-29 16:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-29 16:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-29 16:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-28 20:05 UTC

   The issue has been resolved We apologise for any inconvenience caused

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-29 09:05 UTC

   Some ongoing work on a construction site above the datacenter has impacted the cooling system, we have seen a rise of temperature triggering some hardware safety measure. Temperature is now under control, our datacenter provider is monitoring closely the situation and ready to...

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-29 07:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-29 06:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-28 15:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-28 06:35 UTC

   The issue root cause has been identified and corrected, we are monitoring the service status.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-06-08 11:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-28 10:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-29 12:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-25 12:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-25 09:37 UTC

   From Friday 22/05 13:30 CET to Monday 25/05 11:00 CET, creation of messaging triggers for Serverless Functions was unavailable. Existing triggers still worked as expected, but may have been wrongfully marked in the `error` status by an automatic process. Situation is back to...

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-25 08:05 UTC

   Traces ingestion and query were partially impacted on the fr-par AZ since 23/05/2026 10h45 CEST. We have since resolved the incident and are currently monitoring its progress.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-23 12:40 UTC

   Switchover to main power has been completed successfully. We are back to a nominal state.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-22 11:45 UTC

   Following an infrastructure update, the Kafka clusters were no longer reachable via the private network. The issue has been resolved, and the services are operational again.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-20 08:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-19 12:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-19 12:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-18 13:56 UTC

   The incident affected the API on our DNS Management for Elements. We had an API answer time issue between 14:43 and 14:51.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-18 15:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-18 11:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-13 10:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-11 15:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-29 16:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-06 12:49 UTC

   Customers may have experienced elevated error rates on metrics and logs in Cockpit on the nl-ams and pl-waw regions. The issue has been resolved and service is back to normal.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-06 09:01 UTC

   Customers may have experienced RPN connectivity issues with Dedibox servers in DC5 room 1 rack D13 blocks K and L due to an unreachable RPN switch. Public connectivity was not affected.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-05 20:30 UTC

   Customers may have experienced errors when managing DNS records due to a partial outage on the DNS Management for Elements service. It happened around 22h30 on 2026/05/05

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-27 12:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-05 16:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-05 18:17 UTC

   Customers are now able to create new Dedicated Deployments in the Managed Inference service.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-07 14:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-06 12:51 UTC

   The issue has been fixed. Everything is back to normal since yesterday at 8:30 PM. If you are still encountering an issue please contact our support team.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-11 08:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-05 08:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-06 16:38 UTC

   L'incident est désormais résolu. Pour plus d'information concernant sa résolution, le rapport d'incident est disponible : https://security.scaleway.com/?tcuUid=77cb65ef-456b-45a5-99b7-27eae316a112 Veuillez toutefois noter que la réinitialisation de mot de passe est...

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-26 13:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-04 14:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-04 11:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-06 13:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-01 08:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-06 14:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-30 09:55 UTC

   At 10h43 CET, customers may have experienced network interruptions on Elastic Metal servers located in rack 430B/110 in nl-ams-2

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-06 14:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-30 08:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-06 13:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-28 13:50 UTC

   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...

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-27 15:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-27 12:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-04 12:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-27 07:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-23 14:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-23 08:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-30 12:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-22 08:12 UTC

   Email reception on the pf-012.whm.fr-par.scw.cloud platform was degraded. Emails remained in the queue and were not delivered due to a malfunction. The problem has been fixed and the pending emails have been successfully delivered.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-21 22:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-21 13:07 UTC

   Customers may experience ingestion errors on product metrics due to a load increase on an internal component.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-20 14:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-20 16:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-06 14:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-17 07:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-16 14:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-16 10:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Names an upstream provider: Cloudflare.

1. resolved 2026-04-15 09:44 UTC

   [10:00] Clients facing issues An issue with the update of Imunify on cPanel broke the Cloudflare proxy feature and prevents access to the websites using this feature. The issue is directly caused by : https://imunify360.statuspage.io/incidents/810xhk4nbqnr [10:50] Acknowledged...

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-15 09:36 UTC

   got a temporary api issue between 7:17 UTC to 8:25 UTC.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-14 11:30 UTC

   The issue has been resolved and all services are now operating normally.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-13 07:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-13 14:06 UTC

   No more disruption since 48 hours. Returned to a plain healthy state. No dataloss detected on affected cluster.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-09 15:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-08 15:21 UTC

   The issue has been identified and resolved, and we are monitoring the situation to ensure stability.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-08 13:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-07 11:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-04 22:10 UTC

   Switch has been replaced network is up for the Rack D39

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-03 16:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-27 08:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-01 15:12 UTC

   During a product maintenance, we have noticed an increase of latency and errors. Our team performed a rollback and monitor the situation since then. The instability was seen during approximately two hours (12h20 to 14h UTC).

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-08 07:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-08 07:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-03 16:21 UTC

   The issue has been resolved. Please contact our support team if you have any issue with our SAN.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-31 13:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-30 15:45 UTC

   Start from 30 march 2026 at 15h53 CET, Kapsule cluster creation was not possible. The incident was resolved 30 march 2026 at 17h04.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-27 12:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-27 09:57 UTC

   On March 26, 2026, we experienced an incident affecting Serverless Containers in the following regions: pl-waw: from approximately 11:30 CET to 11:36 CET nl-ams: from approximately 13:30 CET to 13:40 CET During these periods, a platform-level component triggered an automatic...

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-06 08:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-26 14:00 UTC

   We have performed a server maintenance for the cPanel platform 1006. A downtime of 10 min may have occured during the maintenance.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-26 13:30 UTC

   We have performed a server maintenance for the cPanel platform 1005. A downtime of 10 min may have occured during the maintenance.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-26 10:57 UTC

   At 02:25:50 UTC+1, an RPN switch in DC5 Room 1 Rack B15 rebooted, interrupting network traffic for servers attached to it for 10 minutes.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-26 07:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-25 10:34 UTC

   The incident was resolved at 11:22 a.m. CET.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-25 09:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-25 18:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-25 08:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-24 14:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-05-15 09:53 UTC

   The fix have been deployed in every region

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-06 08:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-20 15:49 UTC

   We have identified that a network switch in our fr-par-1 data center was malfunctioning, causing a partial outage for Dedibox dedicated servers. The issue has been resolved and all services are now back to normal. We apologize for any inconvenience this may have caused.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-26 09:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-17 17:18 UTC

   Summary: Following a deployment to release VPC Peering in public beta, a change in DNS resolution within VPC caused DNS issues. These issues only affected Kapsule clusters in full isolation mode using Debian 12/13 containers and were limited to the nl-ams and pl-waw regions....

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-26 09:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-27 10:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-16 20:08 UTC

   A brief issue occured with MongoDB instances in the Paris region (fr-par). Some instances were in an error state but remained reachable. The issue is now fixed.

Excerpts are shortened. Read the full incident on Scaleway's status page.

Names an upstream provider: AWS.

1. resolved 2026-03-17 10:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-16 12:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-16 15:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-16 13:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-13 10:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-12 11:43 UTC

   The incident is fully resolved, and the response times are back to normal.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-26 09:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-12 09:06 UTC

   The incident has been resolved, and we are monitoring the issue still for a long-term fix to prevent the issue from occurring again.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-11 12:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-12 09:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-12 09:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-09 10:09 UTC

   We experienced an elevated error rate when querying Loki custom datasources in the fr-par region. This issue may have affected your ability to retrieve data from these datasources. We encounter 2% error rate on query and 5% on ingestion from 08:52 to 08:53 UTC

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-09 10:38 UTC

   An internal issue has been resolved. Cluster creation in the Paris region (fr-par) is now operational.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-09 09:01 UTC

   Our team has fixed the issue and the redirection service is now up again.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-08 08:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-08 09:56 UTC

   Replacing the faulty switch has restored service at this time.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-09 11:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-05 16:32 UTC

   We have finished monitoring the situation. Container instances are now running without a liveness probe, preventing them from restarting. Now, restarts are only triggered by users applicative errors (e.g. if the container crashes). Note that after our fix made earlier, users...

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-06 10:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-08 09:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-18 21:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-04 15:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-05 14:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-04 14:35 UTC

   A storage full issue occurred due to a failed migration. Additional storage was added to resolve the issue.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-04 14:31 UTC

   The TLS certificate for free domains has expired, causing potential security warnings or access issues. Our teams have acknowledged the issue and are currently deploying new certificates and restarting the service in all affected regions.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-09 18:59 UTC

   After investigation, we have found the root cause. During the scheduled maintenance https://status.scaleway.com/incidents/p2cj27y80n9w, starting on 03/03 at 3:30 PM UTC, we experienced a lot of pressure on our infrastructure, saturating the number of connections of our LB. As a...

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-04 08:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-03 09:16 UTC

   The Key Manager service was unavailable in the it-mil region due to a pod failure for about 10 minutes.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-03 09:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-02 15:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-28 11:13 UTC

   This incident started at 22:27 UTC when started Block Storage incident. At 11:10 UTC, all databases have returned to a plain healthy state.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-28 04:50 UTC

   This incident started at 22:27 UTC when latency began to rise noticeably. At 22:40 UTC, A control‑plane fault caused several disks to be excluded at once from the cluster. The resulting load on the control plane then prevented the cluster from self‑recovering, progressively...

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-06 10:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-13 10:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-10 07:51 UTC

   Customers may have experienced delays when sending emails to Microsoft domains (Outlook, MSN, Hotmail) due to temporary rate limiting. The issue has been resolved and email delivery should now be operating normally.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-27 09:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-04 09:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-26 16:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-27 15:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-02 15:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-26 10:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-26 08:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-03-05 09:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-24 10:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-24 14:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-24 09:30 UTC

   Since 08:45 UTC, we are experiencing a network outage in the PL-WAW region, causing multiple RDB clusters to failover. This may result in brief interruptions for your databases.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-24 09:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-04-06 08:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-24 15:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-23 16:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-23 15:17 UTC

   The issue has been resolved. All custom metrics are now being ingested as expected.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-24 09:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-24 09:29 UTC

   All containers and functions configured in sandbox v1 have their CPU and RAM metrics available in Cockpit as usual. Thank you for your patience.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-20 16:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-20 16:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-20 10:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-18 13:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-18 06:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-18 13:16 UTC

   Only one customer was affected and the timeouts experienced were due to too many requests on the opensearch lb.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-24 15:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-17 15:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-16 17:53 UTC

   A fix have been deployed, all affected IPs have been unlocked.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-16 09:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-18 21:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-13 18:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-13 15:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-13 08:29 UTC

   The switch in rack S1/C29 experienced a crash and rebooted, causing a 5-minute unavailability of the public connectivity for this rack. Timestamps : 2026 Feb 13 03:14 UTC - switch rebooted 2026 Feb 13 03:17 UTC - switch recovered

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-24 15:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-13 09:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-12 09:18 UTC

   Between 8:00 PM CET on February 11, 2026, and 9:00 AM CET on February 12, 2026, approximately 10% of users experienced issues when querying logs from Cockpit. The problem has been fully resolved. We apologize for any inconvenience caused and thank you for your understanding.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-11 13:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-11 13:23 UTC

   The switch issue in our nl-ams-1 data center has been resolved. All affected Dedibox servers should now have normal connectivity.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-11 10:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-09 18:58 UTC

   Latencies are back to nominal, incident is resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-09 10:00 UTC

   Requests are being rejected by the Web Application Firewall (WAF) following an automatic update of the Core Rule Set. Our team is investigating the issue and has rolled back to the previous version of the rules library.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-09 02:18 UTC

   The Dedibox Console is now back to normal operation. We apologize for the inconvenience this may have caused.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-07 09:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-06 13:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-05 12:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-04 08:57 UTC

   Several MySQL servers restarted, some experienced prolonged startup and temporary unavailability. All services are back up. We apologize for any inconvenience caused.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-04 19:12 UTC

   The RPN switch in DC3 room, 4-3 rack C16 experienced issues, causing RPN connectivity interruption in the rack. Public connectivity was not affected. The issue has been resolved, and normal operations have been restored.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-04 17:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-04 13:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-04 08:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-30 17:32 UTC

   Some Dedibox users experienced issues with their previously valid phone numbers being flagged as invalid, preventing consumption. The issue has been resolved and all phone numbers are now correctly validated.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-02-05 14:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-30 02:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-28 11:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-26 18:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-26 16:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-26 16:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-26 09:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-28 10:13 UTC

   Issue has now been resolved. Only deployments between 2026-01-23 14:00 UTC and 2026-01-25 15:00 UTC were impacted. We encourage users who made an update of their function/container inside the time range above, and who are seeing resources in "error" status, with message...

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-24 12:10 UTC

   Since January 23, 17:46 UTC, one of our Block Storage internal API endpoints in the fr-par-3 region has been unable to join his cluster. This has resulted in delays in internal asynchronous tasks until retry with another endpoint. It may also have affected some public tasks too....

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-24 09:08 UTC

   From 14/01 13h28 to 22/01 16h42 UTC cockpit received no logs from Object Storage product. The timeframe was the consequence of a dysfunctional alert that was supposed to handle this case.The problem is fixed and additional monitoring will be added.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-28 10:17 UTC

   After days of monitoring after increasing the LB capacity, the initial issue is now fixed. We still continue to monitor closely the situation though. To summarize, requests on nl-ams containers/functions made between 2026-01-08 and 2026-01-23 08:45 UTC might have failed with 5xx...

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-28 16:28 UTC

   Incident have been resolved. A fix has been implemented.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-16 22:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-16 10:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-26 17:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-14 07:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-14 13:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-13 16:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-13 16:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-12 17:42 UTC

   The intervention is now done, the replacement was made.

Excerpts are shortened. Read the full incident on Scaleway's status page.

1. resolved 2026-01-21 13:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Scaleway's status page.