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...

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...

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: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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: A code release introduced the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: Hardware, power, cooling or another physical failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with high confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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 claude-haiku-5-5 with low confidence (taxonomy v0.2).

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: Hardware or facility. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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.

Affected: Generative API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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.

Affected: Excellence

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

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.

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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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.

Affected: Dedibackup

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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.

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

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

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.