Scaleway
Status impact color legend
  • Black impact: None
  • Yellow impact: Minor
  • Red impact: Major
  • Blue impact: Maintenance
[OBJS] - [world] - Failures on ranged request on SSE enabled objects
Identified - Ranged GetObject requests on SSE-(C/ONE) objects might fail, no impact on user data, a fix has been found and will be deployed shortly.
Mar 24, 2026 - 15:27 CET
[Cockpit] - [nl-ams] - errors on query for Scaleway Logs Datasources
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 23, 2026 - 11:43 CET
Investigating - Some querier pods are not restarting after Kubernetes upgrade, causing errors when querying Scaleway Logs Datasources. This may impact the ability to view and analyze logs.
Mar 23, 2026 - 11:25 CET
[Account API] - fr-par-1 Users can't receive login email
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 19, 2026 - 20:43 CET
Investigating - Users are currently unable to receive login emails due to a technical issue affecting the Account API in the fr-par-1 region.
Mar 19, 2026 - 20:09 CET
[Managed Opensearch] - [fr-par-1] - Create-deployment workflows failure
Investigating - Some create-deployment workflows are failing. This may impact your ability to create new deployments. We are currently investigating the issue.
Mar 17, 2026 - 15:43 CET
[Cockpit] - [fr-par-1] High error rate
Update - We are continuing to investigate this issue.
Mar 17, 2026 - 11:56 CET
Investigating - Numerous workloads are not ready, causing high error rates in the Cockpit service.
Mar 17, 2026 - 11:56 CET
[Generative APIs] - Partial Outage on gpt-oss-120b and mistral-small-3.2-24b-instruct-2506 models
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.
Mar 12, 2026 - 11:20 CET
[Edge Services] - Partial Outage on GET requests when content is fetched from origins
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.
Mar 09, 2026 - 11:24 CET
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.
Mar 09, 2026 - 09:24 CET
[OBJS] - [PAR] - Lifecycle Job Execution
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 06, 2026 - 09:05 CET
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.
Mar 05, 2026 - 12:01 CET
[Transactional Email] - Low IP reputation with Microsoft servers
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.
Feb 27, 2026 - 10:33 CET
[Cockpit] - Resource usage issue
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 24, 2026 - 16:48 CET
Investigating - We have identified an issue on resource usage ingestion.
The monthly ressource usage may be slightly inaccurate due to a delay in 24/02/2026 data processing.
Feb 24, 2026 - 09:46 CET
[WEBHOSTING] SMTP/51.159.208.135 blacklisted on Microsoft/Outlook from classic webhosting service
Identified - Our service is currently experiencing disruption due to blacklisting by Microsoft.
We are actively working with Microsoft to resolve this issue as soon as possible.
Nov 24, 2025 - 19:34 CET
SMS Routing to US Numbers
Update - We are still unable to send SMS to US numbers.
The issue is due to A2P 10DLC regulations, which require registration and approval.
We have submitted the necessary requests to our providers, the approval process takes a minimum of 3 weeks.

We will provide updates as soon as we have more information.
Jul 21, 2025 - 10:30 CEST
Identified - The issue has been identified and a fix is being implemented.
Jul 17, 2025 - 15:14 CEST
Investigating - We are currently experiencing an issue where messages containing a phone number in the USA are not being properly routed by our SMS provider.

A ticket has been opened on their side.
We are actively monitoring the situation and will share updates as soon as available.
Jul 16, 2025 - 12:15 CEST

About This Site

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/

Uptime over the past 90 days. View historical uptime.
Elements - Products Operational
90 days ago
100.0 % uptime
Today
Instances Operational
Elastic Metal Operational
Apple Silicon Operational
Object Storage Operational
Block Storage Operational
Container Registry Operational
Network Operational
Private Network Operational
Public Gateway Operational
Load Balancer Operational
Kubernetes Kapsule Operational
Serverless Functions and Containers Operational
Serverless-Database Operational
Jobs Operational
Databases Operational
Messaging and Queuing Operational
Domains Operational
IoT Hub Operational
Web Hosting Operational
Transactional Email Operational
IAM Operational
Observability Operational
Secret Manager Operational
Environmental Footprint Operational
Developer Tools Operational
Account Operational
Billing Operational
Edge service Operational
Elements Console Operational
Website Operational
Generative API Operational
Managed Inference Operational
APIs Operational
Serverless Container Operational
90 days ago
100.0 % uptime
Today
Data Warehouse Operational
90 days ago
100.0 % uptime
Today
Elements - AZ Degraded Performance
fr-par-1 Operational
fr-par-2 Operational
fr-par-3 Operational
nl-ams-1 Degraded Performance
nl-ams-2 Degraded Performance
nl-ams-3 Degraded Performance
pl-waw-1 Operational
pl-waw-2 Operational
pl-waw-3 Operational
Dedibox - Products Operational
Dedibox Operational
Hosting Operational
SAN Operational
Dedirack Operational
Dedibackup Operational
Domains Operational
RPN Operational
Dedibox Console Operational
Dedibox VPS Operational
Dedibox - Datacenters Operational
DC1 Operational
DC2 Operational
DC3 Operational
DC4 Operational
DC5 Operational
AMS Operational
Miscellaneous Degraded Performance
Excellence Degraded Performance
BookMyName Operational
Saagie - Products Operational
Product-1-ACO Operational
Product-2-BOU Operational
Product-3-BV Operational
Product-4-DN Operational
Product-5-MAT Operational
Product-6-SIPDEV Operational
Product-7-SIPINT Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

[Serverless Containers] - [fr-par] - mandatory operation to prepare for new v1 API (1/2) Apr 1, 2026 08:00-17:00 CEST

On April 1st (between 8 AM and 5 PM UTC), we will perform a mandatory operation in the fr-par region to prepare for the upcoming v1 API (coming soon).

This operation will be carried out in two maintenance windows:
- April 1, 2026
- April 8–9, 2026

Over the course of these three days, changes will be applied to all Serverless Containers namespaces in the fr-par region.

While this operation is seamless most of the time, users may observe the following behaviors:

- Namespaces will pass temporarily in "upgrading" status. This may take up to 15 minutes, depending on the number of resources inside the namespace. During this time, all write operations on the namespace (update namespace, create container, update container, delete container, etc.) will be impossible. Read operations will work as usual.
- Container instances will be created. This is mandatory to ensure the containers are working properly. If a container fails to start, the "status" field will change to "error", and the "error_message" field will show the error, so users can fix it. During that process, users could see multiple instances of their container running, even if it's configured with max_scale = 1, and even if there is no incoming traffic. The Container will downscale as soon as the operation is over.
- Long running requests made during this operation may fail, as we roll out Container instances.
- Crons might be triggered multiple times during the operation. Crons with frequent schedules (such as every minute) might be more impacted.

Please note that during this process, unless the containers cannot start because of an applicative error, the containers will always be reachable.

This process is mandatory to prepare a seamless upgrade to the new v1 API, which will bring enhanced features and improvements. More details here: https://www.scaleway.com/en/docs/serverless-containers/reference-content/v1-migration-guide/

Thank you for your understanding, and we apologize for any inconvenience this may cause.
Posted on Mar 24, 2026 - 10:46 CET

[Serverless Containers] - [fr-par] - mandatory operation to prepare for new v1 API (2/2) Apr 8, 2026 08:00-17:00 CEST

On April 1st (between 8 AM and 5 PM UTC), we will perform a mandatory operation in the fr-par region to prepare for the upcoming v1 API (coming soon).

This operation will be carried out in two maintenance windows:
- April 1, 2026
- April 8–9, 2026

Over the course of these three days, changes will be applied to all Serverless Containers namespaces in the fr-par region.

While this operation is seamless most of the time, users may observe the following behaviors:

- Namespaces will pass temporarily in "upgrading" status. This may take up to 15 minutes, depending on the number of resources inside the namespace. During this time, all write operations on the namespace (update namespace, create container, update container, delete container, etc.) will be impossible. Read operations will work as usual.
- Container instances will be created. This is mandatory to ensure the containers are working properly. If a container fails to start, the "status" field will change to "error", and the "error_message" field will show the error, so users can fix it. During that process, users could see multiple instances of their container running, even if it's configured with max_scale = 1, and even if there is no incoming traffic. The Container will downscale as soon as the operation is over.
- Long running requests made during this operation may fail, as we roll out Container instances.
- Crons might be triggered multiple times during the operation. Crons with frequent schedules (such as every minute) might be more impacted.

Please note that during this process, unless the containers cannot start because of an applicative error, the containers will always be reachable.

This process is mandatory to prepare a seamless upgrade to the new v1 API, which will bring enhanced features and improvements. More details here: https://www.scaleway.com/en/docs/serverless-containers/reference-content/v1-migration-guide/

Thank you for your understanding, and we apologize for any inconvenience this may cause.
Posted on Mar 24, 2026 - 10:51 CET
Mar 24, 2026
[MongoDB] - FR-PAR - DNS resolution failure
Resolved - This incident has been resolved.
Mar 24, 15:32 CET
Investigating - We are currently experiencing an issue with DNS resolution for entries related to the Private Network, which is affecting MongoDB SRV record lookups. This is preventing some customers from connecting to their MongoDB instances when using Private Network endpoints. Our engineering teams are actively investigating and working to resolve the issue as quickly as possible. We sincerely apologise for the inconvenience and will share updates as soon as more information becomes available.
Mar 24, 14:55 CET
Software Upgrade on Core Router in WAW Region
Completed - The scheduled maintenance has been completed.
Mar 24, 14:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 24, 09:00 CET
Update - We will be undergoing scheduled maintenance during this time.
Mar 12, 10:30 CET
Scheduled - A planned software upgrade is scheduled on a core router in the WAW region. During this maintenance window redundancy for network connections in the region will be temporarily unavailable. Packet loss or service disruption is not expected.
Mar 12, 10:29 CET
Mar 23, 2026

Unresolved incident: [Cockpit] - [nl-ams] - errors on query for Scaleway Logs Datasources.

Mar 22, 2026

No incidents reported.

Mar 21, 2026

No incidents reported.

Mar 20, 2026
[Dedibox dedicated servers] - fr-par-1 DC3 - Room 4-6 Rack A08 PUB switch is down
Resolved - 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.
Mar 20, 16:49 CET
Update - Situation should be resolved since 4:45 UTC
We had multiples spare devices with issues which explain the late resolution.
We wish you a nice Friday and week-end
Mar 20, 16:48 CET
Update - Issue is taking longer than expected.
We are still on the bridge with local technicians to bring back up the switch and it's associate services
Mar 20, 16:11 CET
Update - We are currently experiencing a Public network issue in rack DC3 Room 4-6 Rack A08. This is causing a loss of internet traffic for connected dedicated servers.
Network Switch is in an incorrect state, we have asked our local technicians to replace it.
Mar 20, 12:28 CET
Investigating - We are currently experiencing a Public network issue in rack DC3 Room 4-6 Rack A08. This is causing a loss of internet traffic for connected dedicated servers. We are investigating the root cause with our local technicians.
Mar 20, 11:37 CET
Mar 19, 2026

Unresolved incident: [Account API] - fr-par-1 Users can't receive login email.

Mar 18, 2026
[Elastic Metal] - [fr-par-2] - EM-RV Unable to order
Resolved - This incident has been resolved.
Mar 18, 22:25 CET
Investigating - Our Elastic Metal servers EM-RV are currently unavailable for rental due to being stuck in a cleaning state. Existing instances are unaffected.
Mar 4, 16:50 CET
Mar 17, 2026
[VPC][AMS][WAW] DNS Resolution Incident in Isolated Kapsule Clusters
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.
Mar 17, 18:18 CET
[Scaleway - Domains] Radix TLD maintenance on March 16–17: renewals/restores/registrations/transfers unavailable
Completed - The scheduled maintenance has been completed.
Mar 17, 18:01 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 16, 18:00 CET
Scheduled - Due to the Radix TLD registry transition to Tucows on March 17,  Radix TLD operations will be paused from Mon, March 16 through Tue, March 17.
Due to the Radix TLD registry’s transition from CentralNic to Tucows (effective 17 March 2026), there will be a maintenance window from Mon, March 16 at 18:00 CET (UTC+1) to Tue, March 17 at 18:00 CET (UTC+1).
Impacted Radix TLDs:
  - .fun
  - .host
  - .online
  - .press
  - .pw
  - .site
  - .space
  - .store
  - .tech
  - .uno
  - .website

Impact (only for Radix TLD domains):
Unavailable: new registrations, renewals, transfers, restores, change owner and NS updates

Unaffected: existing Radix TLD domains will continue to resolve normally (websites, DNS, and email should continue to work).

What you can do:
If your Radix domain is expiring soon, please renew before March 16 to avoid any issue.
No action is needed if you’re not planning to renew your Radix TLD domains, or perform other modifications during this period.
We’ll resume normal processing as soon as the maintenance completes.
If you have any questions, please contact our support team.

Thank you for your understanding.
Mar 11, 10:58 CET
[PAR][NETWORK] Upgrade Backbone routers
Completed - The scheduled maintenance has been completed.
Mar 17, 18:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 17, 08:00 CET
Scheduled - We will be performing a planned maintenance on one of our core backbone routers located in the Paris DC3 data center.
The maintenance will take place 03/17/2026 between 08:00 to 18:00 CET time

This router is part of a fully redundant architecture, and traffic will be offloaded to the remaining infrastructure devices during the operation.
However, despite this offload and redundancy, some temporary side effects may occur during the maintenance window, including:
- Brief connectivity interruptions
- Temporary increases in latency
- Packet loss
- Routing changes
- Network reconvergence

These impacts may affect services hosted in Paris and, due to interconnections between sites, could also potentially impact Amsterdam.
We are taking all necessary measures to minimize disruption and ensure a swift return to normal operations.
Feb 27, 15:50 CET
[Object Storage] - [World] - Download issues with AWS CLI
Resolved - This incident has been resolved.
Mar 17, 11:00 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 16, 22:30 CET
Identified - The error has been identified and we are deploying a fix to correct it.
Mar 16, 19:07 CET
Investigating - Some clients may experience issues when attempting to download objects with a starting range > 0.
The 'GetObject' command is not affected.
Mar 16, 18:16 CET
Mar 16, 2026
[MongoDB] - [fr-par] Instances in error state but reachable
Resolved - 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.
Mar 16, 21:08 CET
[Cockpit] - [world] Sync grafana datasources are broken
Resolved - This incident has been resolved.
Mar 16, 16:28 CET
Investigating - The regional API in Milan became unreachable from Paris, preventing Grafana data sources from being listed. This may impact your ability to manage and visualise your monitoring data.
Mar 16, 09:30 CET
[Payment] - Double payment for SEPA
Resolved - This incident has been resolved.
Mar 16, 14:09 CET
Investigating - Our payment service provider has made double payments for some clients. We are working with them to cancel the duplicate payments.
Mar 13, 19:02 CET
[Public Gateway] - [fr-par-1] Issue with Create/Update of Public gateway
Resolved - This incident has been resolved.
Mar 16, 13:36 CET
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.
Mar 16, 13:36 CET
[MongoDB] OpsManager update
Completed - The scheduled maintenance has been completed.
Mar 16, 12:30 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 16, 11:30 CET
Scheduled - This maintenance will cause a brief downtime of a few seconds during the failover process.

During this window, you will not be able to make any changes to your MongoDB resources (e.g., creating/deleting instances or creating/restoring snapshots). Please ensure that no critical operations are scheduled during this time.

This update is part of our ongoing efforts to keep the system up to date and ensure the stability of our services.
Mar 6, 11:25 CET
Mar 15, 2026

No incidents reported.

Mar 14, 2026

No incidents reported.

Mar 13, 2026
[API Gateway] - [pl-waw] Region disconnected from api.scaleway.com
Resolved - This incident has been resolved.
Mar 13, 11:30 CET
Update - We are continuing to monitor for any further issues.
Feb 27, 17:31 CET
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
Feb 27, 13:49 CET
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.
Feb 27, 12:39 CET
[DC3] - Public switch down room 46 - D2
Resolved - This incident has been resolved.
Mar 13, 11:02 CET
Monitoring - The switch has been replaced but still under monitoring by our team.
Mar 13, 09:23 CET
Investigating - Since 02:02AM, the public switch is down in DC3 in room 46 - D2. This may impact the connectivity of some services.
Mar 13, 08:19 CET
Mar 12, 2026
[Instance Orchestration] - [fr-par] API Not available
Resolved - The incident is fully resolved, and the response times are back to normal.
Mar 12, 12:43 CET
Identified - We have identified the likely culprit and applied a mitigation patch. We are closely monitoring the situation.
Mar 12, 11:41 CET
Investigating - The Instance Orchestration API is currently not available in the fr-par region. This may affect your ability to manage your instances.
Mar 12, 11:24 CET
[Cockpit] - [fr-par] performance issues with custom DS read/write
Resolved - This incident has been resolved.
Mar 12, 10:07 CET
Investigating - Since 09/03/2026, metrics and logs read and write in custom DS suffer performance issues.
We are investigating this issue.
Mar 10, 10:54 CET
[Cockpit] - [fr-par] Ingestion errors on custom metrics datasources
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.
Mar 12, 10:06 CET
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.
Mar 11, 19:03 CET
Investigating - Elevated error rate on ingestion for custom metrics data sources in fr-par for some customers.
Mar 11, 16:29 CET
[Cockpit] - [fr-par-1, fr-par-2, fr-par-3] Partial error on metrics ingestion
Resolved - This incident has been resolved.
Mar 12, 10:04 CET
Update - We are continuing to investigate this issue.
Mar 11, 10:17 CET
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.
Mar 11, 10:17 CET
Mar 11, 2026
[Instance Orchestration] - [fr-par-2] - No public IPv4 available
Resolved - This incident has been resolved.
Mar 11, 13:54 CET
Investigating - We are currently out of stock of IPv4 on FR-PAR-2. No new instances with public IPv4 can be created.
Mar 11, 12:54 CET
Mar 10, 2026
← Incident History Powered by Atlassian Statuspage