Welcome to the Scaleway Status website. Here, you can view the status of all Scaleway services across all products and availability zones (AZs).
You can check how subscribe, manage your email status updates and how to receive status notifications on Slack here: https://www.scaleway.com/en/docs/account/reference-content/scaleway-status-updates/
On Thursday, July 23rd, 2026, we will upgrade the version of the database that stores product data.
Impact Existing hubs and devices will remain connected correctly. Partial service unavailability:
- The IoT Hub API will not be available during the migration process. - The auto-provisioning feature will not work while the API is down. - Connection status will not be updated during the maintenance (e.g.: connected_device_count, last_activity_at, is_connected ); however, the same information displayed in Cockpit will remain accurate.
Support Our team is available to assist with any questions regarding this migration. Please contact support through your usual channels. Posted on
Jul 21, 2026 - 17:12 CEST
Resolved -
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 intermittantly and only form some job runs only between 21/07/2026 22:00:00 CEST and 22/07/2026 01:49:00 CEST and between 22/07/2026 03:44:00 CEST and 22/07/2026 05:30:00. The number of impacted job runs represent approximately the tenth of our average daily job runs. This is an informative status and no corrective action was required by us. Please check if you need to run your job again. We apologize for the inconvenience.
Jul 22, 14:57 CEST
Completed -
Scheduled maintenance done.
Jul 22, 14:29 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 22, 14:00 CEST
Update -
We will be undergoing scheduled maintenance during this time.
Jul 22, 11:55 CEST
Scheduled -
In order to fix a missconfiguration on a router, our network team will perform the maintenance on the 22th of July 2026 at 02:00PM CEST. This will impact dedibox servers located on DC2 room 108. During the whole maintenance, your Dedibox server will keep Internet reachability. RPN network will be down during the maintenance. We expect the downtime to last a maximum of 10 minutes. We are sorry for the inconvenience.
Jul 22, 11:51 CEST
Resolved -
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.
Jul 22, 11:55 CEST
Identified -
Following incident on Compute instances (https://status.scaleway.com/incidents/bsp2y5fysy9w), a few Serverless Containers and namespaces on fr-par region have been stuck in transient statuses (updating/deleting) during the night.
Not all resources were impacted, only a fraction on one part of our infrastructure (~1/10). On this part, impacted resources were either:
- updated between 2026-07-21 21:07 UTC and 2026-07-21 22:05 UTC - or deleted between 2026-07-21 21:33 UTC and 2026-07-22 03:18 UTC
We have fixed the statuses, so resources are not stuck anymore. But, this would require impacted users to update or delete again their namespaces/containers if the status is in error with one of these error messages:
- For previously "updating" containers: Last container update could not be processed successfully. Please try again - For previously "deleting" containers: Container could not be succesfully deleted. Please try again - For previously "updating" namespaces: Last namespace update could not be processed successfully. Please try again - For previously "deleting" namespaces: Namespace could not be succesfully deleted. Please try again
Resolved -
This incident has been resolved.
Jul 22, 06:55 CEST
Monitoring -
The situation has returned to normal
Jul 22, 05:53 CEST
Investigating -
We are currently investigating this issue.
Jul 22, 05:30 CEST
Monitoring -
The Kapsule public API is available again.
Jul 22, 03:41 CEST
Update -
The situation is stable.
All products are now operational except for the Kapsule public API, which is still unavailable.
Jul 22, 02:27 CEST
Update -
Disk I/O operations are starting to recover, which should begin resolving the issue for the instances.
Jul 22, 01:35 CEST
Update -
Our team is currently working on solving the issue.
Jul 22, 00:50 CEST
Update -
We are still investigating this critical issue with the utmost priority.
Jul 21, 23:39 CEST
Update -
We are continuing to investigate this issue.
Jul 21, 23:13 CEST
Investigating -
Following a crash of one node on the block storage cluster at 20h15 UTC, some VMs are stuck. The oncall team is investigating it.
Jul 21, 23:03 CEST
Resolved -
This incident has been resolved.
Jul 22, 03:33 CEST
Identified -
11:13 CEST to 11:48 CEST Users may have experienced high error rates or timeouts during this 30-minute window. Our engineering team has identified and resolved the issue.
Jul 20, 12:13 CEST
Resolved -
This incident has been resolved since 19:15 UTC.
Jul 21, 21:50 CEST
Investigating -
Some free domains may currently display a default hosting page or resolve incorrectly due to inconsistencies in domain mappings. Our teams are investigating and working to restore the correct configuration.
Jul 21, 21:09 CEST
Resolved -
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.
Jul 21, 18:44 CEST
Identified -
Since around 12:30 PM UTC, several internal connections to the Scaleway API within the it-mil region are failing. As a result: - Pushes to rg.it-mil.scw.eu are failing and returning an "HTTP 500" error. - Serverless Containers deployments are failing (resources stuck in creating) (list is not exhaustive)
Our team is actively working on a fix as we speak, we apologise for any inconvenience caused by this incident.
Jul 21, 18:11 CEST
Resolved -
This incident has been resolved.
Jul 21, 10:28 CEST
Identified -
A mandatory maintenance operation targeting one of the Block Storage is taking longer than planned. Some clients may experience latencies during write operations on sbs_5k and sbs_15K volumes. We are monitoring it and working to tune this operation to limit impact.
Jul 20, 21:07 CEST
Resolved -
This incident has been resolved.
Jul 20, 16:51 CEST
Investigating -
Following a network issue, the product APIs were unavailable for a few minutes. The issue was immediately resolved by our teams.
Jul 20, 16:50 CEST
Resolved -
This incident has been resolved.
Jul 17, 15:21 CEST
Investigating -
A dedibox switch in DC5, room 1, rack A59 has an unstable connection to the upstream router. We need to replace the SFPs. This will result in a brief loss of connectivity for servers connected to this switch.
Jul 17, 12:06 CEST
Resolved -
This incident has been resolved.
Jul 17, 10:56 CEST
Investigating -
Installation/reinstallation and reboot workflows via API or console are not available for Apple Silicon. Currently in use mac are still operationals and reachable.
Jul 17, 09:32 CEST
Resolved -
This incident has been resolved.
Jul 16, 08:58 CEST
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 15, 18:30 CEST
Update -
We are continuing to investigate this issue.
Jul 15, 17:37 CEST
Investigating -
We are investigating an issue affecting login for some accounts that have multiple organizations linked to them. Accounts with a single organization are not impacted.
Jul 15, 17:32 CEST
Resolved -
This incident has been resolved.
Jul 15, 19:20 CEST
Update -
We are continuing to investigate this issue.
Jul 2, 10:04 CEST
Update -
We are continuing to investigate this issue.
Jun 30, 16:42 CEST
Investigating -
Customers may experience slowness and errors when pulling/pushing images to the Container Registry in fr-par. Some pulls/pushes may take up to 30 minutes or fail entirely. This may also cause delays or failures in Serverless Containers and Functions deployments.
Jun 30, 08:00 CEST
Resolved -
This incident has been resolved.
Jul 15, 19:12 CEST
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 13, 16:03 CEST
Identified -
The issue has been found, fixed, tested and is being rolled out.
Jul 13, 15:56 CEST
Investigating -
Customers may experience missing tags when listing tags on Container Registry regional endpoints. Pulling images by tag or digest is not impacted. The Container Registry API is not impacted and returns the correct list of tags.
Jul 13, 11:39 CEST
Completed -
The scheduled maintenance has been completed.
Jul 15, 10:01 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 10:00 CEST
Scheduled -
Overview On Wednesday, July 15th, 2026, we will implement a breaking change to the Secret Manager API as part of our permission system migration.
Impact Before July 15th :
If the user has permissions for all current and future projects: Neither organization_id nor project_id is required. If the user has permissions for all projects or only specific projects: The project_id is required.
After July 15th : If the user has permissions for all current and future projects: The organization_id is required and sufficient. If the user has permissions for all projects or only specific projects: The project_id is required (no change).
Affected Services - Scaleway GitHub Action - No impact - External Secrets Operator - No impact - Direct API integrations - Update required
Timeline - Date: Wednesday, July 15th, 2026 - Duration: Immediate effect (no downtime expected) - Status: Planned
Support Our team is available to assist with any questions regarding this migration. Please contact support through your usual channels.
Jul 3, 10:30 CEST
Completed -
The scheduled maintenance has been completed.
Jul 15, 08:00 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 05:00 CEST
Scheduled -
We will be performing a planned maintenance on one of our Dedibox routers located in the Amsterdam IMDC data center. The maintenance will take place 15th of July 2026 between 05:00 to 8:00 CET time. Expect multiples impacts during this maintenance window.
This router is the public gateway of the following racks in AMS1 Dedibox Fabric : - 6.12.17 - 6.12.22 - 6.12.29 - 6.12.60 - 6.12.67 - 6.12.71 - 6.12.72 - 6.12.73 - 6.12.74
Customers having servers in these racks should expect Public traffic impact. RPN should not be impacted at any time.
We are taking all necessary measures to minimize disruption and ensure a swift return to normal operations.
Jun 29, 17:13 CEST
Resolved -
This incident has been resolved.
Jul 12, 12:48 CEST
Investigating -
Customers may experience a partial outage of public connectivity on servers attached to the public switch Room 4 4-6 rack 1 in DC3.
Jul 12, 11:13 CEST
Resolved -
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.
Jul 10, 15:32 CEST
Identified -
The issue has been identified and a fix is being implemented.
Jul 8, 14:06 CEST
Investigating -
Instances that were restored through snapshots can produce new snapshots, but cannot restore those snapshots. We are currently investigating this issue.
Jul 7, 11:04 CEST
Resolved -
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.
Jul 10, 12:45 CEST
Monitoring -
Update: Connectivity has been partially restored at around 9:30 AM. We are monitoring the situation.
Jul 10, 09:32 CEST
Investigating -
Starting from 07:30 CET, users may experience connectivity issues or failed requests when accessing their Serverless Containers in the nl-ams region. This issue is under investigation by our team.
Jul 10, 07:57 CEST
Resolved -
This incident has been resolved.
Jul 10, 09:45 CEST
Update -
We are continuing to investigate this issue.
Jul 10, 09:43 CEST
Investigating -
Customers may experience failures when creating Spark clusters in the fr-par region due to an issue with an internal dependency.
Jul 9, 16:35 CEST
Resolved -
This incident has been resolved.
Jul 9, 18:36 CEST
Investigating -
Customers may experience unresponsiveness when using the mistral-medium-3.5-128b model due to an instability on an internal component.
Jul 9, 18:19 CEST
Resolved -
This incident has been resolved.
Jul 9, 17:19 CEST
Update -
We are still working on a fix for this issue.
Jul 6, 10:14 CEST
Identified -
We are working on a fix. Instabilities may still appear when using mistral-medium-3.5-128b model. But overall the service remain usable.
Jun 22, 10:15 CEST
Investigating -
Customers may experience instabilities when using the mistral-medium-3.5-128b model in the Generative APIs service in the fr-par region.
Jun 19, 14:36 CEST
Resolved -
This incident has been resolved.
Jul 9, 15:28 CEST
Investigating -
Customers may experience transient 5xx errors when using the qwen3.6-35b-a3b model due to instabilities on an internal component.
Jul 3, 12:21 CEST
Resolved -
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.
Jul 9, 10:06 CEST
Resolved -
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 continuing to monitor the situation.
Jul 9, 09:00 CEST