Scaleway Status

Status impact color legend

Black impact: None
Yellow impact: Minor
Orange impact: Major
Blue impact: Maintenance

Update - A maintenance will happen on some servers between 10/03/2024 3PM CEST and 10/04/2024 6PM CEST to upgrade the resources. There should be no service interruption.
Oct 03, 2024 - 15:02 CEST

Investigating - Even after the fixes, we're still experiencing time-outs and the error "Reduce your request rate".
Our team is actively working towards a lasting resolution, thank you for your patience and understanding.
Oct 01, 2024 - 12:36 CEST

Monitoring - Following a faulty fix deployed Friday 27 Sept at 10PM CEST, the object storage solution experienced instability. At 14:30PM CEST on the 28 Sept, we began rolling out a downgrade of that fix. Everything was deployed at 6PM CEST and the service is stable again.
Sep 28, 2024 - 18:12 CEST

Investigating - We are experiencing instability on the Object Storage solution in fr-par region since 8PM UTC on friday 27/09, resulting in HTTP 503 errors for customers.
We are currently investigating this issue.
Sep 28, 2024 - 13:40 CEST

[Dedibox] [Billing] - Installations fees wrongly billed with Dediscount

Investigating - The installation fees with the Dedidscount for a 36 months commitment are actually billed, while they shouldn't be. Our Dedibox team is already aware of this issue and is working on it.
Oct 01, 2024 - 15:00 CEST

[KAPSULE] Maintenance on Kubernetes clusters to automatically migrate from NAT IPs to Routed IPs

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 01, 2024 - 08:00 CEST

Scheduled - Maintenance is scheduled for your managed Kubernetes clusters to automatically migrate from NAT IPs to Routed IPs. This action will only affect clusters which have not been manually migrated by September 30th.

Please note that node public IP addresses that are not flexible will be change.

Impact: ~1 minute downtime for single-node clusters (no downtime if multiple nodes).
For more information and guidance on manually migrating to Routed IPs, please refer to our documentation below.

https://www.scaleway.com/en/docs/containers/kubernetes/reference-content/move-kubernetes-nodes-routed-ip/
Oct 1, 2024 08:00 - Oct 7, 2024 08:00 CEST

[Webhosting][classic] Mail backup processes stuck

Investigating - The daily mail backup process is blocked and recent mail backups are unavailable for some of our classic hosting customers. This does not affect website or database backups. Our teams are currently investigating.
Sep 30, 2024 - 16:48 CEST

[SAN] san-dc2-32.rpn.online.net is slowned down

Monitoring - Our team monitoring continues.
Updates to follow.
Sep 24, 2024 - 12:51 CEST

Identified - san-dc2-32.rpn.online.net is slowed down during a maintenance operation. Clients on this SAN can notice unusual slowness. We are closely monitoring it.
Sep 09, 2024 - 16:48 CEST

[Dedibackup] issue on Dedibackup connections

Investigating - We have noticed that problems with connecting to the dedibackup service can occur.
We will get back to you as soon as we have more information on the situation.
Apr 06, 2023 - 12:23 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). We are currently making a few adjustments to enhance your navigation and overall experience. Over the next couple of weeks, you will see some changes to the website. Our team is here to assist you, and we appreciate your patience.

Elements - Products Degraded Performance

Instances Operational

Object Storage Degraded Performance

Scaleway Glacier Operational

Block Storage Operational

Elastic Metal Operational

Apple Silicon M1 Operational

Kubernetes Kapsule Operational

Container Registry Operational

Private Network Operational

Load Balancer Operational

Domains Operational

Serverless Functions and Containers Operational

Jobs Operational

Databases Operational

IoT Hub Operational

Web Hosting Operational

Observability Operational

Transactional Email Operational

Network Operational

Account API Operational

Billing API Operational

Elements Console Operational

Dedibox - Products Degraded Performance

Dedibox Degraded Performance

Hosting Degraded Performance

SAN Operational

Dedirack Operational

Dedibackup Operational

Domains Operational

RPN Operational

Dedibox Console Operational

Elements - AZ Under Maintenance

fr-par-1 Operational

fr-par-2 Operational

fr-par-3 Operational

nl-ams-1 Operational

pl-waw-1 Under Maintenance

nl-ams-2 Operational

pl-waw-2 Operational

nl-ams-3 Operational

pl-waw-3 Operational

Dedibox - Datacenters Operational

DC2 Operational

DC3 Operational

DC5 Operational

AMS Operational

Miscellaneous Operational

Excellence Operational

Website Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Scheduled Maintenance

[INSTANCE] Deprecation of NAT IP on Instances API Oct 7, 2024 00:15 - Oct 8, 2024 00:15 CEST

Creating NAT enabled Instance (with parameter routed_ip_enabled=false ) is not supported anymore as of 7th October.
If you have any script calling the API directly to create Instances with NAT IPs, please switch to Routed IPs. If you are using our CLI or Terraform adapter, please update to the latest version to support these changes.
Posted on Sep 17, 2024 - 16:25 CEST

[KAPSULE] Maintenance on Kubernetes clusters to automatically migrate from NAT IPs to Routed IPs Oct 7, 2024 08:00 - Oct 14, 2024 08:00 CEST

Maintenance is scheduled for your managed Kubernetes clusters to automatically migrate from NAT IPs to Routed IPs. This action will only affect clusters which have not been manually migrated by September 30th.

Please note that node public IP addresses that are not flexible will be change.

Impact: ~1 minute downtime for single-node clusters (no downtime if multiple nodes).
For more information and guidance on manually migrating to Routed IPs, please refer to our documentation below.

https://www.scaleway.com/en/docs/containers/kubernetes/reference-content/move-kubernetes-nodes-routed-ip/
Posted on Jul 15, 2024 - 11:40 CEST

[KAPSULE] Maintenance on Kubernetes clusters to automatically migrate from NAT IPs to Routed IPs Oct 14, 2024 08:00 - Oct 21, 2024 08:00 CEST

Past Incidents

Oct 3, 2024

Unresolved incident: [Storage]-Object Storage instability.

Oct 2, 2024

No incidents reported.

Oct 1, 2024

[Serverless functions/containers] Intermittent DNS Failures

Resolved - This incident has been resolved.
Oct 1, 17:08 CEST

Monitoring - A fix has been implemented and we are monitoring the results.
Sep 30, 11:54 CEST

Investigating - We are currently investigating an issue with intermittent DNS failures that may cause Functions and Containers deployments to fail with an "Error" status.
We are working to resolve the issue as soon as possible. We apologize for the inconvenience and will provide further updates on our progress.
Sep 30, 10:20 CEST

[Support] - Partial unavailability

Resolved - The situation is now back to normal.
Thank you for your patience and understanding.
Oct 1, 07:48 CEST

Identified - Support may be unavailable by phone at certain times during the day, and delays in processing tickets are to be expected.
Thank you for your patience and understanding.
Sep 30, 09:55 CEST

Sep 30, 2024

[Instances] Scheduled maintenance on Instances to automatically move from NAT IPs to Routed IPs

Completed - The scheduled maintenance has been completed.
Sep 30, 12:00 CEST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 1, 08:00 CEST

Scheduled - Maintenance is scheduled for your Instances (excluding Kubernetes Instances) to automatically switch from NAT IPs to Routed IPs.

This action will only affect Instances which have not previously been manually migrated.

Impact: ~1 minute downtime for VM restart. Broken VM if configuration uses NAT IP information.

For more information and guidance on manually moving your Instances to Routed IPs, please refer to our documentation.

Migration will happen in multiple batches by AZ between September 1st and November 30th 2024.
Aug 8, 17:24 CEST

Sep 29, 2024

[Online console]- Ticket creation error

Resolved - This incident has been resolved.
Sep 29, 11:41 CEST

Investigating - We are currently investigating this issue.
Sep 29, 10:42 CEST

Sep 28, 2024

Sep 27, 2024

[Website] Scaleway Website down

Resolved - This incident has been resolved.
Sep 27, 11:17 CEST

Update - We are continuing to investigate this issue.
Sep 27, 11:17 CEST

Investigating - www.scaleway.com is down.
Only the website, console/Api is up.
Sep 27, 11:15 CEST

[DC5] switch down - room 1 1 - rack A9

Resolved - The swicth has been changed
This incident has been resolved
Sep 27, 09:02 CEST

Investigating - We currently have switch down in DC5 room 1 1 rack A9 .

Our engineers are working on resolving this.
Sep 27, 08:27 CEST

[DC2]-Switch Down, Room 203 Rack B, D and F

Resolved - This incident has been resolved.
Sep 27, 08:33 CEST

Investigating - We currently have a switch down in DC2 room 203 block B, D, F.

Our engineers are working on resolving this.
Sep 26, 20:29 CEST

[DC2]-Switch Down 203b rack I12

Resolved - This incident has been resolved.
Sep 27, 08:33 CEST

Update - We currently have both switchs down in DC2 room 203 .

Our engineers are working on resolving this.
Sep 26, 21:42 CEST

Update - We are continuing to investigate this issue.
Sep 26, 21:40 CEST

Investigating - We currently have a switch down in DC2 room 203 block A, B, C.

Our engineers are working on resolving this.
Sep 26, 21:33 CEST

Sep 26, 2024

Sep 25, 2024

[DC5]- Switch down - Room 1.1 rackB9

Resolved - The switch has been replaced.
Sep 25, 21:45 CEST

Update - The switch on DC5 room 1.1 bay 9 is down.
We apologize for the inconvenience and are doing everything we can to get things back to normal.
Sep 25, 19:41 CEST

Identified - The issue has been identified and a fix is being implemented.
Sep 25, 19:39 CEST

[FR-PAR] [NL-AMS] Object Storage instability

Resolved - This incident has been resolved.
Sep 25, 17:28 CEST

Update - We are continuing to monitor for any further issues.
Sep 25, 11:54 CEST

Update - We are continuing to monitor for any further issues.
Sep 25, 11:42 CEST

Monitoring - A fix has been implemented and we are monitoring the results.
Sep 25, 11:42 CEST

Identified - We identified the issue, mitigated the incident, and have been working on a bugfix to prevent this issue from happening again.
Sep 25, 10:43 CEST

Investigating - We are experiencing instability on the Object Storage solution in nl-ams and fr-par regions since last night, resulting in a HTTP 503 error for customers.
Sep 25, 09:48 CEST

Sep 24, 2024

[Serverless Functions/Containers] [All regions] Infrastructure maintenance

Completed - The scheduled maintenance has been completed.
Sep 24, 17:00 CEST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 24, 14:00 CEST

Scheduled - A maintenance will be performed on our infrastructure for both Serverless Functions and Containers products in all regions.

During the maintenance, multiple core components of our infrastructure will be upgraded. Some hiccups can be experienced (see "impacts" section below); we apologize for any inconvenience.

Impacts:

During the maintenance, clients might encounter the following disturbances:
- functions/containers unexpected restarts: as we restart underlying instances, running functions/containers will need to be relocated to different instances. Depending on the functions/containers configuration (min scale or how they handle termination), some 5xx can also be experienced.
- a few transient 403 and 5xx errors: during functions/containers restart, but also while system components are being restarted
Sep 23, 16:30 CEST

Sep 23, 2024

[ServerlessFunction/Billing] Important Update: Correction to Serverless Functions Billing

Resolved - Update: Serverless Functions Billing Corrections
We're pleased to confirm that our billing system has been corrected, and invoices for September Serverless Functions Consumption usage are accurate. If you have any further questions or concerns, feel free to reach out to us.
You can also refer to our documentation for more information about Serverless Functions billing: https://www.scaleway.com/en/docs/faq/serverless-functions/#how-am-i-billed-for-serverless-functions
Thank you for your understanding, and again for your patience throughout this issue.
Sep 23, 10:08 CEST

Investigating - We've identified an incident that resulted in underbilling for Serverless Functions Consumption starting from May.

We apologize for any inconvenience this may have caused.

Current Situation:

We will be issuing accurate invoices for Serverless Functions Consumption usage starting from September, reflecting the correct usage and charges.

No surprises: we won't charge you for the underbilled months (May to August) to ensure your billing remains accurate and transparent.

Serverless Containers continue to be billed accurately, with no issues or disruptions.

Additional Resources:

For detailed information about Serverless Functions billing, please visit our documentation:

https://www.scaleway.com/en/docs/faq/serverless-functions/#how-am-i-billed-for-serverless-functions

Thank you for your understanding, and please don't hesitate to reach out with any questions or concerns.
Sep 12, 11:55 CEST

Sep 22, 2024

No incidents reported.

Sep 21, 2024

[RPN-SAN] Connection issue on san-ssd-3.rpn.online.net

Resolved - This incident has been resolved.
Sep 21, 17:06 CEST

Monitoring - A fix has been implemented and we are monitoring the results.
Sep 21, 17:03 CEST

Investigating - We are currently investigating this issue.
Sep 21, 16:53 CEST

Sep 20, 2024

[AMS] - AMS container registry pull/push may fail for some requests

Resolved - This incident has been resolved.
Sep 20, 16:45 CEST

Update - Serverless functions on nl-ams region are affected by this incident, as they are using registry from this region.

Despite retries done internally to push the images built from the clients codes, a few number of users might nonetheless see their function ending up in error, with the following message: "error on function build step : cannot push to scaleway container registry, retry later or contact support".

If that is the case, retrying later (5 min) should be enough to mitigate the issue, as registry errors are unlikely to happen multiple times in a row during 5 minutes timeframe.

If the issue continues after, please contact the support.
Sep 9, 09:32 CEST

Update - We are continuing to investigate this issue.
Sep 4, 20:07 CEST

Investigating - We are investigating some slight error rate on AMS registry
Sep 4, 20:02 CEST

Sep 19, 2024

[DNS]-Cloudflare safe DNS services have blacklisted the scw.cloud domain

Resolved - The incident was resolved.

Please contact Support if you still face DNS issues.
Sep 19, 17:00 CEST

Investigating - Cloudflare safe DNS services have blacklisted the scw.cloud domain, and subdomains. Please use the 1.1.1.1 variant or another DNS resolver to fix the issue
Sep 19, 13:38 CEST

[Network]-Power issue

Resolved - The incident has been resolved.

Please contact our Support if you face any power issues
Sep 19, 14:00 CEST

Monitoring - A fix has been implemented and we are monitoring the results.
Sep 19, 13:09 CEST

Investigating - Public access down in dc3/s45 racks: c10,c11,c12
RPN access down in dc3/s45 racks: c10
Sep 19, 13:08 CEST