Scaleway Status

Resolved: This incident has been resolved.

Investigating: Our Elastic Metal servers EM-RV are currently unavailable for rental due to being stuck in a cleaning state. Existing instances are unaffected.

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

Identified: Since 03/03/26, daily Lifecycle jobs have failed to execute for some buckets.

Status: Root cause identified; fix ready for deployment. Action: Once deployed, jobs will run immediately to clear the backlog.

Resolved: This incident has been resolved.

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

Identified: The error has been identified and we are deploying a fix to correct it.

Investigating: Some clients may experience issues when attempting to download objects with a starting range > 0. The 'GetObject' command is not affected.

Resolved: This incident has been resolved.

Monitoring: The switch has been replaced but still under monitoring by our team.

Investigating: Since 02:02AM, the public switch is down in DC3 in room 46 - D2. This may impact the connectivity of some services.

Resolved: 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. Timeline:

09:39 UTC — Incident began after the VPC Peering deployment. 11:30 UTC — First rollback completed on nl-ams-1; investigation and reproduction efforts began. ~16:10 UTC — Confirmed the scope was limited to Debian 12/13 containers in full isolation mode. 16:13 UTC — Full rollback completed on nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3.

The issue is now resolved. We are continuing to analyze the root cause and will provide a permanent fix.

Resolved: This incident has been resolved.

Investigating: We want to inform you that the issue affecting the creation and updating of Public Gateways in the fr-par-1 Availability Zone has now been resolved.

Between 18:50 UTC on March 13, 2026 and 10:20 UTC on March 16, 2026, some customers may have experienced difficulties with these operations. We sincerely apologize for any inconvenience caused.

Our team has addressed the issue, and services are back to normal.

If you encountered any problems during this period or need further assistance, please contact our support team.

Thank you for your understanding.

Resolved: 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. Timeline:

09:39 UTC — Incident began after the VPC Peering deployment. 11:30 UTC — First rollback completed on nl-ams-1; investigation and reproduction efforts began. ~16:10 UTC — Confirmed the scope was limited to Debian 12/13 containers in full isolation mode. 16:13 UTC — Full rollback completed on nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3.

The issue is now resolved. We are continuing to analyze the root cause and will provide a permanent fix.

Identified: We are noticing an increase in issues with Microsoft, with the message: "temporarily rate limited due to IP reputation." Our team is already taking action to mitigate the issue, but you may notice some delays and retries when sending to Outlook, MSN, or Hotmail. Microsoft has acknowledged the issue and is currently investigating on their side.

Resolved: This incident has been resolved.

Investigating: Since 09/03/2026, metrics and logs read and write in custom DS suffer performance issues. We are investigating this issue.

Resolved: This incident has been resolved.

Investigating: We are continuing to investigate this issue.

Investigating: Since 1:00 (CEST), partial errors on metrics ingestion for Custom and SCW metrics, this should result in no data loss with a proper retry mechanism.

Resolved: The incident has been resolved, and we are monitoring the issue still for a long-term fix to prevent the issue from occurring again.

Monitoring: We have identified that the elevated error rate on ingestion for custom metrics data sources in fr-par is due to a constant increase in the number of series from Serverless. We are working on a solution to address this issue.

Investigating: Elevated error rate on ingestion for custom metrics data sources in fr-par for some customers.

Investigating: We are continuing to investigate this issue.

Investigating: Numerous workloads are not ready, causing high error rates in the Cockpit service.

Monitoring: Edge Services is experiencing a partial outage, causing truncated HTTP content on GET requests when the content is fetched from the origin. This issue is consecutive to a software upgrade on our stack. A rollback has been performed and we are monitoring the situation.

Identified: Edge Services is randomly serving truncated HTTP content on GET requests, when the content is fetched from the origin. This behavior is consecutive to a software upgrade on our stack. A rollback is planned today.

Investigating: We are currently experiencing a partial outage affecting the gpt-oss-120b and mistral-small-3.2-24b-instruct-2506 models. This may result in failures when attempting to use these models.

Our team already works to resolve this issues.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: This disconnection was caused by one of our transit provider misbehaving, we are removing this transit from the network paths until they have explained and stabilized their network

Investigating: The API Gateway service in the pl-waw region is currently experiencing connectivity issues with api.scaleway.com. This may impact the ability to manage and access certain services through the API.

Resolved: The incident is fully resolved, and the response times are back to normal.

Identified: We have identified the likely culprit and applied a mitigation patch. We are closely monitoring the situation.

Investigating: The Instance Orchestration API is currently not available in the fr-par region. This may affect your ability to manage your instances.

Resolved: This incident has been resolved.

Investigating: Since 09/03/2026, metrics and logs read and write in custom DS suffer performance issues. We are investigating this issue.

Resolved: This incident has been resolved.

Investigating: We want to inform you that the issue affecting the creation and updating of Public Gateways in the fr-par-1 Availability Zone has now been resolved.

Between 18:50 UTC on March 13, 2026 and 10:20 UTC on March 16, 2026, some customers may have experienced difficulties with these operations. We sincerely apologize for any inconvenience caused.

Our team has addressed the issue, and services are back to normal.

If you encountered any problems during this period or need further assistance, please contact our support team.

Thank you for your understanding.

Resolved: This incident has been resolved.

Investigating: Our Elastic Metal servers EM-RV are currently unavailable for rental due to being stuck in a cleaning state. Existing instances are unaffected.

Resolved: This incident has been resolved.

Investigating: Since 09/03/2026, metrics and logs read and write in custom DS suffer performance issues. We are investigating this issue.

Resolved: This incident has been resolved.

Investigating: Since 09/03/2026, metrics and logs read and write in custom DS suffer performance issues. We are investigating this issue.

Resolved: 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. Timeline:

09:39 UTC — Incident began after the VPC Peering deployment. 11:30 UTC — First rollback completed on nl-ams-1; investigation and reproduction efforts began. ~16:10 UTC — Confirmed the scope was limited to Debian 12/13 containers in full isolation mode. 16:13 UTC — Full rollback completed on nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3.

The issue is now resolved. We are continuing to analyze the root cause and will provide a permanent fix.

Resolved: 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. Timeline:

09:39 UTC — Incident began after the VPC Peering deployment. 11:30 UTC — First rollback completed on nl-ams-1; investigation and reproduction efforts began. ~16:10 UTC — Confirmed the scope was limited to Debian 12/13 containers in full isolation mode. 16:13 UTC — Full rollback completed on nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3.

The issue is now resolved. We are continuing to analyze the root cause and will provide a permanent fix.

Resolved: 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. Timeline:

09:39 UTC — Incident began after the VPC Peering deployment. 11:30 UTC — First rollback completed on nl-ams-1; investigation and reproduction efforts began. ~16:10 UTC — Confirmed the scope was limited to Debian 12/13 containers in full isolation mode. 16:13 UTC — Full rollback completed on nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3.

The issue is now resolved. We are continuing to analyze the root cause and will provide a permanent fix.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: This disconnection was caused by one of our transit provider misbehaving, we are removing this transit from the network paths until they have explained and stabilized their network

Investigating: The API Gateway service in the pl-waw region is currently experiencing connectivity issues with api.scaleway.com. This may impact the ability to manage and access certain services through the API.

Resolved: 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. Timeline:

09:39 UTC — Incident began after the VPC Peering deployment. 11:30 UTC — First rollback completed on nl-ams-1; investigation and reproduction efforts began. ~16:10 UTC — Confirmed the scope was limited to Debian 12/13 containers in full isolation mode. 16:13 UTC — Full rollback completed on nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3.

The issue is now resolved. We are continuing to analyze the root cause and will provide a permanent fix.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: This disconnection was caused by one of our transit provider misbehaving, we are removing this transit from the network paths until they have explained and stabilized their network

Investigating: The API Gateway service in the pl-waw region is currently experiencing connectivity issues with api.scaleway.com. This may impact the ability to manage and access certain services through the API.

Resolved: 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. Timeline:

09:39 UTC — Incident began after the VPC Peering deployment. 11:30 UTC — First rollback completed on nl-ams-1; investigation and reproduction efforts began. ~16:10 UTC — Confirmed the scope was limited to Debian 12/13 containers in full isolation mode. 16:13 UTC — Full rollback completed on nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3.

The issue is now resolved. We are continuing to analyze the root cause and will provide a permanent fix.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: This disconnection was caused by one of our transit provider misbehaving, we are removing this transit from the network paths until they have explained and stabilized their network

Investigating: The API Gateway service in the pl-waw region is currently experiencing connectivity issues with api.scaleway.com. This may impact the ability to manage and access certain services through the API.

Resolved: 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. Timeline:

09:39 UTC — Incident began after the VPC Peering deployment. 11:30 UTC — First rollback completed on nl-ams-1; investigation and reproduction efforts began. ~16:10 UTC — Confirmed the scope was limited to Debian 12/13 containers in full isolation mode. 16:13 UTC — Full rollback completed on nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3.

The issue is now resolved. We are continuing to analyze the root cause and will provide a permanent fix.

Resolved: This incident has been resolved.

Investigating: Our payment service provider has made double payments for some clients. We are working with them to cancel the duplicate payments.

Investigating: Some create-deployment workflows are failing. This may impact your ability to create new deployments. We are currently investigating the issue.