Scaleway

Is Scaleway Down Right Now? Check if there is a current outage ongoing.

Scaleway is currently Degraded

Last checked from Scaleway's official status page

Historical record of incidents for Scaleway

Report: "[WEBHOSTING] - [PAR2/PAR] - Latency on pf-012 websites"

Last update
investigating

We are currently investigating this issue.

Report: "[IOC] - Elevated error rate on api-compute"

Last update
resolved

This incident has been resolved.

investigating

Following a deployment of api-compute, we notice an elevated rate of 500 errors, mainly on fr-par-2, endpoints POST /ips and POST /servers.

Report: "[VPC] - DHCP, DNS traffic lost on fr-par-2"

Last update
resolved

This incident has been resolved.

monitoring

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

investigating

[fr-par-2] From 6:04 UTC to 7:28 UTC, customers could experience DHCP & DNS & NTP loss through VPC when using VPC's managed service. The situation is now resolved.

Report: "[Kapsule] Some clusters control plane cannot be reached on fr-par"

Last update
investigating

Issue started at around 8:14 CEST Some clusters unreachable via their LB

Report: "[DC5] - Public switch issue in DC5 room 1 1 rack D27"

Last update
investigating

We are continuing to investigate this issue.

investigating

We have detected a switch down in DC5 room 1 1 rack D27 Servers in that rack currently have no public network access and are unreachable. An intervention is planned and a technician will carry out all the necessary checks.

Report: "[DC5] - Public switch issue in DC5 room 7 rack C57 bloc A"

Last update
identified

We have detected a switch down in DC5 room 7 rack C57 bloc A Servers in that rack currently have no public network access and are unreachable. =================== Since 08.06.25 at 18h00. Issue has been forwarded to our team for resolution.

Report: "[pl-waw] Users can't connect to their functions/containers endpoints Affected products: Serverless Functions/Containers"

Last update
investigating

Since 2025-06-07 09:20 UTC, around half of the users cannot call their functions/containers endpoints in pl-waw region. Users are experiencing "connect: connection refused" or "Could not connect to server" errors. At first glance, this seems caused by a LB failure. We apologize for any inconvenience. We are on it.

Report: "[NETWORK] [DC3] - DC3 room 4-5 rack C7/C8/C9 unreachable"

Last update
resolved

Public switches in racks C7/C8/C9 went down at 5:34PM CEST Everything went back at 5:42PM CEST

Report: "Object storage issue on a small subset of buckets on pl-waw region"

Last update
Monitoring

13 buckets on the whole PL-WAW region have been impacted. We will contact the specific customers with a message coming soon from our support."

Investigating

On Friday 28th of May at 09.00AM UTC, we did a scheduled operation. Since this operation, a small subset of buckets may suffer from a bad behavior that our technical team is currently investigating.

Report: "[BILLING] DDX2ELT clients SEPA payment failures"

Last update
Identified

On June 2nd, a bug in our Payment API caused SEPA payment failures for some DDX2LT clients. As a fallback, the system tried to charge by credit card, but some of those payments also failed.We have identified the issue and are working on a fix. Once resolved, we will provide appropriate solutions for affected clients.

Report: "Object storage issue on a small subset of buckets on pl-waw region"

Last update
monitoring

13 buckets on the whole PL-WAW region have been impacted. We will contact the specific customers with a message coming soon from our support."

investigating

On Friday 28th of May at 09.00AM UTC, we did a scheduled operation. Since this operation, a small subset of buckets may suffer from a bad behavior that our technical team is currently investigating.

Report: "[BILLING] DDX2ELT clients SEPA payment failures"

Last update
identified

On June 2nd, a bug in our Payment API caused SEPA payment failures for some DDX2LT clients. As a fallback, the system tried to charge by credit card, but some of those payments also failed. We have identified the issue and are working on a fix. Once resolved, we will provide appropriate solutions for affected clients.

Report: "[Cloud-Hosting]- Maintenance"

Last update
Completed

The scheduled maintenance has been completed.

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

Server: cPanel platforms 1004, 1005, 1006, 1007, 1010, 1011Maintenance: Server updateA downtime of 10 min can be expected on each platform during the maintenance

Report: "[Dédibox] Installation issue on Ubuntu 24.04"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

We are currently experiencing a technical issue with the installation of Ubuntu 24.04 LTS, our teams are currently working on it, we will keep you informed.

Report: "[Dédibox] Installation issue on Ubuntu 20.04"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

We are currently experiencing a technical issue with the installation of Ubuntu 20.04, our teams are currently working on it, we will keep you informed.

Report: "[KAPSULE] ControllerUnpublishVolume fails on volume migrated to SBS"

Last update
Resolved

This incident has been resolved.

Monitoring

A fix is being rolled out we are monitoring

Update

We are continuing to investigate this issue.

Investigating

Starting this morning around 11:35 CEST migrated volumes can't get detached anymore

Report: "[KAPSULE] ControllerUnpublishVolume fails on volume migrated to SBS"

Last update
resolved

This incident has been resolved.

monitoring

A fix is being rolled out we are monitoring

investigating

We are continuing to investigate this issue.

investigating

Starting this morning around 11:35 CEST migrated volumes can't get detached anymore

Report: "[GAPI] - fr-par - gemma3 and whisperX model unavailable"

Last update
monitoring

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

investigating

We are aware of issues affecting customers of the gemma-3-27b-it model since 15:00. We are currently investigating theses issues.

Report: "[Webhosting][classic] Err 500/SSL issues"

Last update
Resolved

This incident has been resolved.

Monitoring

Our team has set up a fix and recovery work is now under the supervision of our engineers.

Investigating

Several classic webhosting customers may experiencing 500/error SSL certificate errors.Our team is already working on it.

Report: "[Instances] Migration of b_ssd volumes to SBS"

Last update
Update

We will be undergoing scheduled maintenance during this time.

Scheduled

From June 3rd until June 12th, we are migrating b_ssd volumes, b_ssd snapshot, b_ssd snapshots and unified snapshots to Scaleway Block Storage (SBS). If your organization is affected, you have received a communication via email including the list of impacted resources. No action is required on your part, volumes will remain available during the migration window.

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Report: "[Webhosting][classic] Err 500/SSL issues"

Last update
resolved

This incident has been resolved.

monitoring

Our team has set up a fix and recovery work is now under the supervision of our engineers.

investigating

Several classic webhosting customers may experiencing 500/error SSL certificate errors. Our team is already working on it.

Report: "[Kapsule] [fr-par] - K8s integrated dashboards are unreachable"

Last update
Resolved

This incident has been resolved.

Investigating

The dashboard are no longer reachable on fr-par.

Report: "[Kapsule] [fr-par] - K8s integrated dashboards are unreachable"

Last update
resolved

This incident has been resolved.

investigating

The dashboard are no longer reachable on fr-par.

Report: "[Dedibox RPN] RPNv2 connectivity issue between DC"

Last update
Investigating

We are investigating a problem that generated RPNv2 connectivity issue between our datacenters this morning around 07:52 UTC

Report: "[Dedibox RPN] RPNv2 connectivity issue between DC"

Last update
investigating

We are investigating a problem that generated RPNv2 connectivity issue between our datacenters this morning around 07:52 UTC

Report: "[Dedibox RPN] - DC3 room 4-6 - RPN instability"

Last update
resolved

A faulty link on a router generated packet loss and connectivity issues on the RPN network in DC3 room 4-6 between Friday May 30th and Monday June 02nd. This is now resolved.

Report: "[SUPPORT] Unavailability of support"

Last update
Resolved

This incident has been resolved.

Identified

Due to circumstances beyond our control, support will be exceptionally unavailable from 6 PM tonight until 10 PM.We apologize for this inconvenience.

Report: "[SUPPORT] Unavailability of support"

Last update
resolved

This incident has been resolved.

identified

Due to circumstances beyond our control, support will be exceptionally unavailable from 6 PM tonight until 10 PM. We apologize for this inconvenience.

Report: "[SUPPORT]-Unavailability of support"

Last update
Resolved

This incident has been resolved.

Identified

Due to circumstances beyond our control, support will be exceptionally unavailable from 6 PM tonight until 10 PM.We apologize for this inconvenience.

Report: "[SUPPORT]-Unavailability of support"

Last update
resolved

This incident has been resolved.

identified

Due to circumstances beyond our control, support will be exceptionally unavailable from 6 PM tonight until 10 PM. We apologize for this inconvenience.

Report: "[VPS] -VPS proxy is down"

Last update
Resolved

This incident has been resolved.

Monitoring

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

Identified

VPS management page and several endpoints are returning a 504 Gateway Time-out error. Our engineers are doing everything they can to resolve this quickly.

Report: "[VPS] -VPS proxy is down"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

VPS management page and several endpoints are returning a 504 Gateway Time-out error. Our engineers are doing everything they can to resolve this quickly.

Report: "[Serverless Functions/Containers] [fr-par] users might experience issues creating custom domains"

Last update
Resolved

The root cause has been identified. A limit was reached, preventing new domain challenges to be created since 2025-05-26 06:42 UTC, thus leading to errors for new domains creation. This affected only a small part of the fr-par infrastructure (~20% of users).We are going to fix the limit, and add monitoring, so it doesn't happen again.Sorry again, and thanks for your understanding

Monitoring

The issue has been fixed. We have not found the root cause yet, but it's still under investigation. However, users should be able to create new custom domains.Sorry again for any inconvenience.

Identified

A bug prevents users to create new custom domains on their functions/containers. It affects around 20% of the clients in fr-par. For these users, custom domains end up in error after around 3 minutes, even if CNAME configuration is correct. Already created custom domains are not affected.We are on it. Sorry about the inconvenience.

Report: "[Network]-No RPN/PUB for servers located in AMS1/H2/EE15 bloc K and M"

Last update
Resolved

This incident has been resolved.

Investigating

We are currently investigating this issue.

Report: "[Serverless Functions/Containers] [fr-par] users might experience issues creating custom domains"

Last update
resolved

The root cause has been identified. A limit was reached, preventing new domain challenges to be created since 2025-05-26 06:42 UTC, thus leading to errors for new domains creation. This affected only a small part of the fr-par infrastructure (~20% of users). We are going to fix the limit, and add monitoring, so it doesn't happen again. Sorry again, and thanks for your understanding

monitoring

The issue has been fixed. We have not found the root cause yet, but it's still under investigation. However, users should be able to create new custom domains. Sorry again for any inconvenience.

identified

A bug prevents users to create new custom domains on their functions/containers. It affects around 20% of the clients in fr-par. For these users, custom domains end up in error after around 3 minutes, even if CNAME configuration is correct. Already created custom domains are not affected. We are on it. Sorry about the inconvenience.

Report: "[Network]-No RPN/PUB for servers located in AMS1/H2/EE15 bloc K and M"

Last update
resolved

This incident has been resolved.

investigating

We are currently investigating this issue.

Report: "[K8S] Migration to Network VPC"

Last update
Completed

The scheduled maintenance has been completed.

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

We will migrate Kubernetes clusters to a network VPC to enable stricter isolation.Check our documentation for more informationhttps://www.scaleway.com/en/docs/kubernetes/how-to/manage-allowed-ips/No downtime or service impact is expected.Note: This upgrade will not apply to clusters using legacy private gateways. These clusters will continue to operate without changes.Here the schedule for each region : WAR: 19/05 - 20/05AMS: 21/05 - 23/05PAR: 26/05 - 30/05

Report: "[Console] Users can't validate their phone numbers"

Last update
Resolved

This incident has been resolved.

Identified

Phone validation isn't possible on the Scaleway console due to a technical issue.Our team is currently investigate this issue.

Report: "[COCKPIT] Users cannot access Grafana"

Last update
Resolved

This incident has been resolved.

Investigating

Customers can not access Grafana.

Report: "[Console] Users can't validate their phone numbers"

Last update
resolved

This incident has been resolved.

identified

Phone validation isn't possible on the Scaleway console due to a technical issue. Our team is currently investigate this issue.

Report: "[COCKPIT] Users cannot access Grafana"

Last update
resolved

This incident has been resolved.

investigating

Customers can not access Grafana.

Report: "[Dedibox RPN] - DC3 room 4-6 - RPN instability"

Last update
Resolved

A faulty link on a router generated packet loss and connectivity issues on the RPN network in DC3 room 4-6 between Friday May 30th and Monday June 02nd.This is now resolved.

Report: "[Dédibox] Installation issue on Ubuntu 20.04"

Last update
Monitoring

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

Identified

We are currently experiencing a technical issue with the installation of Ubuntu 20.04, our teams are currently working on it, we will keep you informed.

Report: "[Dédibox] Installation issue on Ubuntu 24.04"

Last update
Monitoring

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

Identified

We are currently experiencing a technical issue with the installation of Ubuntu 24.04 LTS, our teams are currently working on it, we will keep you informed.

Report: "[Cockpit]-Grafana high latencies"

Last update
Resolved

This incident has been resolved.

Monitoring

Since 9:47:08 UTC users may experience errors when trying to connect to their Grafana or manage their Grafana Users.Ingestion / Alerting is not impactedIncident is no longer live since 13:35 UTCSituation under investigation

Investigating

We are currently investigating this issue.

Report: "[Cockpit]-Grafana high latencies"

Last update
resolved

This incident has been resolved.

monitoring

Since 9:47:08 UTC users may experience errors when trying to connect to their Grafana or manage their Grafana Users. Ingestion / Alerting is not impacted Incident is no longer live since 13:35 UTC Situation under investigation

investigating

We are currently investigating this issue.

Report: "[ELEMENTS] Multiples elements products are unavailable on FR-PAR-3"

Last update
Resolved

This incident has been resolved.

Monitoring

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

Investigating

We are currently investigating this issue.

Report: "[DEDIBOX VPS]- Inability to manage VPS servers"

Last update
Resolved

This incident has been resolved.

Monitoring

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

Update

We are continuing to work on a fix for this issue.

Identified

An issue regarding VPS servers management is currently preventing customers from managing their instances. Deployed servers are unaffected.

Report: "[ELEMENTS] Multiples elements products are unavailable on FR-PAR-3"

Last update
resolved

This incident has been resolved.

monitoring

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

investigating

We are currently investigating this issue.

Report: "[Network]-No RPN/PUB for servers located in AMS1/H2/EE17 bloc D"

Last update
Resolved

This incident has been resolved.

Investigating

We are currently investigating this issue.

Report: "[DEDIBOX VPS]- Inability to manage VPS servers"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

We are continuing to work on a fix for this issue.

identified

An issue regarding VPS servers management is currently preventing customers from managing their instances. Deployed servers are unaffected.

Report: "[SECRET MANAGER] - "CreateSecretVersion" and "AccessSecretVersion" down in fr-par."

Last update
Resolved

This incident has been resolved.

Update

We are continuing to monitor for any further issues.

Monitoring

A fix has been implemented since 7:15UTC / 9:15 CET and the service has been reestablished. We are monitoring the results.

Identified

We are implementing a fix.

Investigating

Our Secret Manager product is currently out of service in the fr-par region since 05h18 UTC. the ‘CreateSecretVersion’ and ‘AccessSecretVersion’ methods are unusable.We apologize for the inconvenience and our engineers are working hard to resolve this quickly.

Report: "[KEY MANAGER] - Key Manager down in fr-par"

Last update
Resolved

This incident has been resolved.

Monitoring

A fix has been implemented since 7:15UTC / 9:15 CET and the service has been reestablished. We are monitoring the results.

Identified

We are implementing a fix

Investigating

Our KeyManager product is currently out of service in the fr-par region since 05h18 UTC.We apologize for the inconvenience and our engineers are working hard to resolve this quickly.

Report: "[Network]-No RPN/PUB for servers located in AMS1/H2/EE17 bloc D"

Last update
resolved

This incident has been resolved.

investigating

We are currently investigating this issue.

Report: "[KEY MANAGER] - Key Manager down in fr-par"

Last update
resolved

This incident has been resolved.

monitoring

A fix has been implemented since 7:15UTC / 9:15 CET and the service has been reestablished. We are monitoring the results.

identified

We are implementing a fix

investigating

Our KeyManager product is currently out of service in the fr-par region since 05h18 UTC. We apologize for the inconvenience and our engineers are working hard to resolve this quickly.

Report: "[SECRET MANAGER] - "CreateSecretVersion" and "AccessSecretVersion" down in fr-par."

Last update
resolved

This incident has been resolved.

monitoring

We are continuing to monitor for any further issues.

monitoring

A fix has been implemented since 7:15UTC / 9:15 CET and the service has been reestablished. We are monitoring the results.

identified

We are implementing a fix.

investigating

Our Secret Manager product is currently out of service in the fr-par region since 05h18 UTC. the ‘CreateSecretVersion’ and ‘AccessSecretVersion’ methods are unusable. We apologize for the inconvenience and our engineers are working hard to resolve this quickly.

Report: "[WEBHOSTING] - Blacklist Microsoft"

Last update
Identified

The IP 51.159.208.135 of our Webhosting platform is blacklisted by Microsoft.We are currently working on it.

Report: "[WEBHOSTING] - Blacklist Microsoft"

Last update
identified

The IP 51.159.208.135 of our Webhosting platform is blacklisted by Microsoft. We are currently working on it.

Report: "[Console]-Organization Settings and Support Tickets Pages Temporarily Unavailable"

Last update
Resolved

The issue appeared at 3pm, after a new release. We rollbacked to the latest stable state and we will be merging a fix for what happened as soon as possible.

Investigating

Due to internal technical updates, the Organization Settings and Support Tickets pages are currently unavailable. We appreciate your patience and understanding as we work to restore access as soon as possible.

Report: "[COCKPIT] Scheduled maintenance on Cockpit"

Last update
Completed

The scheduled maintenance has been completed.

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

We will be performing necessary upgrades on Cockpit databases to improve future performance and reliability on 19/05/2025.During the maintenance window, you may experience short latencies when accessing dashboards. We recommend you do not create new dashboards or edit existing ones during that window to avoid side effects. No impact is expected on all other actions.We apologize for any inconvenience this may cause and appreciate your understanding. We'll keep you informed as the maintenance progresses.

Report: "[Console]-Organization Settings and Support Tickets Pages Temporarily Unavailable"

Last update
resolved

The issue appeared at 3pm, after a new release. We rollbacked to the latest stable state and we will be merging a fix for what happened as soon as possible.

investigating

Due to internal technical updates, the Organization Settings and Support Tickets pages are currently unavailable. We appreciate your patience and understanding as we work to restore access as soon as possible.

Report: "[DC2] - Public switch issue in DC2 room S101 G22 bloc N"

Last update
Resolved

This incident has been resolved.

Identified

All the servers are back up and running on block M.Our engineers are continuing their investigations on block N.Thank you for your patience and understanding.

Investigating

We have detected a switch down in DC2 room S101 G22 bloc N.Servers in that rack currently have no network access and are unreachable.===================25.05.25 05h32 UTCIssue has been forwarded to our team for resolution.

Report: "[AMS] - Public and private switch issue in DC AMS rack EE22 room hall2"

Last update
Resolved

This incident has been resolved.

Monitoring

The servers are starting to recover on this switch.Thank you for your patience.

Investigating

We have detected a switch down in AMS rack EE22 room hall2.Servers in that rack currently have no network access and are unreachable.===================24.05.25 12.13 UTCIssue has been forwarded to our team for resolution.

Report: "[DC2] - Public switch issue in DC2 room S101 G22 bloc N"

Last update
resolved

This incident has been resolved.

identified

All the servers are back up and running on block M. Our engineers are continuing their investigations on block N. Thank you for your patience and understanding.

investigating

We have detected a switch down in DC2 room S101 G22 bloc N. Servers in that rack currently have no <public/private> network access and are unreachable. =================== 25.05.25 05h32 UTC Issue has been forwarded to our team for resolution.

Report: "[AMS] - Public and private switch issue in DC AMS rack EE22 room hall2"

Last update
resolved

This incident has been resolved.

monitoring

The servers are starting to recover on this switch. Thank you for your patience.

investigating

We have detected a switch down in AMS rack EE22 room hall2. Servers in that rack currently have no <public/private> network access and are unreachable. =================== 24.05.25 12.13 UTC Issue has been forwarded to our team for resolution.

Report: "[DC5] - Private switch issue in DC5 room S1 Rack C34"

Last update
Investigating

We have detected a switch down in DC5 room S1 Rack C34.Servers in that rack currently have no network access and are unreachable.===================26.05.25 09h41 UTCIssue has been forwarded to our team for resolution.

Report: "[DC5] - Private switch issue in DC5 room S1 Rack C34"

Last update
investigating

We have detected a switch down in DC5 room S1 Rack C34. Servers in that rack currently have no <public/private> network access and are unreachable. =================== 26.05.25 09h41 UTC Issue has been forwarded to our team for resolution.

Report: "[BOOKMYNAME] BookMyName API timeouts"

Last update
Resolved

This incident has been resolved.

Update

We are continuing to work on a fix for this issue.

Identified

We are currently experiencing slowdowns in certain operations to thedomain name registries.All operations are automatically restarted by our teams, so you don't have to take any action yourself.The problem has been potentially identified, and a patch is currently being studied to restore normal operation.We are continuing our analysis and will update this page as soon as new information becomes available.

Report: "[BOOKMYNAME] BookMyName API timeouts"

Last update
resolved

This incident has been resolved.

identified

We are continuing to work on a fix for this issue.

identified

We are currently experiencing slowdowns in certain operations to the domain name registries. All operations are automatically restarted by our teams, so you don't have to take any action yourself. The problem has been potentially identified, and a patch is currently being studied to restore normal operation. We are continuing our analysis and will update this page as soon as new information becomes available.

Report: "[COCKPIT] - all-regions - Data visualisation in Grafana partially affected for new projects"

Last update
Resolved

This incident has been resolved.

Identified

In all new projects created after 19/05/2025 3:30 PM, Datasources may not be properly synchronized in Grafana and hence may not be visualised. Data ingestion and query is not affected.A fix is under deployment.

Report: "[COCKPIT] - all-regions - Data visualisation in Grafana partially affected for new projects"

Last update
resolved

This incident has been resolved.

identified

In all new projects created after 19/05/2025 3:30 PM, Datasources may not be properly synchronized in Grafana and hence may not be visualised. Data ingestion and query is not affected. A fix is under deployment.

Report: "[DC3] - Public switch issue in room 4-5 s45-d9.dc3, s45-d10-dc3"

Last update
Resolved

This incident has been resolved.

Monitoring

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

Identified

We have detected a switch down in room 4-5 s45-d9.dc3, s45-d10-dc3.Servers in that rack currently have no public network access and are unreachable.12.05.25 00h37 CESTIssue has been forwarded to our team for resolution.

Report: "[Registry] - [fr-par] - Instabilities"

Last update
Resolved

This incident has been resolved.

Monitoring

As of 2025/05/04 13:00 CEST, the service degradation affecting the container registry has been resolved. The registry has since been operating normally, and our team will continue to monitor it to ensure ongoing stability.

Investigating

Registry is unusually slow, with a lot of latencies and instabilities, causing trouble to other services such as serverless container and function too.

Report: "[DC2] - Public switch issue in room 203-B rack J5"

Last update
Resolved

This incident has been resolved.

Monitoring

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

Identified

We have detected a switch down in room 203-B rack J5Servers in that rack currently have no public network access and are unreachable.Network team is currently investigating the issue.

Report: "[GAPI] - fr-par - gemma3 and whisperX model unavailable"

Last update
Monitoring

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

Investigating

We are aware of issues affecting customers of the gemma-3-27b-it model since 15:00. We are currently investigating theses issues.

Report: "[Account] Captcha verification failed"

Last update
Resolved

This incident has been resolved.

Monitoring

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

Identified

No more sign up possible due to captcha error. We are currently investigating

Report: "[DC3] - Public switch issue in room 4-5 s45-d9.dc3, s45-d10-dc3"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

We have detected a switch down in room 4-5 s45-d9.dc3, s45-d10-dc3. Servers in that rack currently have no public network access and are unreachable. 12.05.25 00h37 CEST Issue has been forwarded to our team for resolution.

Report: "[Registry] - [fr-par] - Instabilities"

Last update
resolved

This incident has been resolved.

monitoring

As of 2025/05/04 13:00 CEST, the service degradation affecting the container registry has been resolved. The registry has since been operating normally, and our team will continue to monitor it to ensure ongoing stability.

investigating

Registry is unusually slow, with a lot of latencies and instabilities, causing trouble to other services such as serverless container and function too.

Report: "[DC2] - Public switch issue in room 203-B rack J5"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

We have detected a switch down in room 203-B rack J5 Servers in that rack currently have no public network access and are unreachable. Network team is currently investigating the issue.

Report: "[Account] Captcha verification failed"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

No more sign up possible due to captcha error. We are currently investigating

Report: "[DC2] Public switch issue in DC2 Room 101 Rack A20"

Last update
Monitoring

Swith has been replaced per a new one and all the customer servers seems back for the business.

Investigating

We have detected that public switch was down in DC2 Room 101 Rack A20.Servers in that rack currently have no network access and are unreachable.

Report: "[DC2] Public switch issue in DC2 Room 101 Rack A20"

Last update
monitoring

Swith has been replaced per a new one and all the customer servers seems back for the business.

investigating

We have detected that public switch was down in DC2 Room 101 Rack A20. Servers in that rack currently have no network access and are unreachable.

Report: "[DC2] - Public switch issue in DC2 Room 101 - s101-g27-13.dc2"

Last update
resolved

This incident has been resolved.

identified

We are continuing to work on a fix for this issue.

identified

We have detected a switch down in DC2 Room 101 - s101-g27-13.dc2 Servers in that rack currently have no public network access and are unreachable. =================== Since 17.05.25 01h53 UTC. Issue has been forwarded to our team for resolution.

Report: "[Serverless Jobs] some schedules may execute at unexpected times"

Last update
resolved

The incident has been resolved

monitoring

The fix has been deployed and we are monitoring the results.

identified

The issue has been identified and a fix has been prepared, it will be deployed as soon as possible

Report: "[Dedibox]-C57/1/DC5 - RPN switch issue"

Last update
resolved

RPN service was unreachable during 11 minutes for the associated servers. Start time : 2025-05-16 16:15 CEST End time : 2025-05-16 16:26 CEST

Report: "[VPC][FR-PAR1] Network disruption"

Last update
resolved

This incident has been resolved.

monitoring

All products above VPC and Instance have been recovered since 10.30 AM UTC. A public postmortem will be available as soon as possible.

investigating

Most of impacted products (Instance, Kapsule, LbaaS, Serverless) have recovered since 10:10 UTC, some Load Balancers are still being fixed, our technical team is working on it.

investigating

We are continuing to investigate this issue.

investigating

Fully resolved on VPC network side, some products are still impacted.

investigating

We are continuing to investigate this issue.

investigating

We encountered an issue with our VPC product. A network outage happened between 09:24 UTC to 09:29 UTC in FR-PAR-1. During this time-frame VPC related services might have been impacted. These related services are Instances, Kubernetes, Load Balancer, Databases, Network, Serverless Jobs. The root cause has been found.

Report: "[VPC][FR-PAR1] DNS Resolution Disruption"

Last update
resolved

This incident has been resolved.

investigating

Partial VPC DNS loss from 14:33 UTC to 14:36 UTC and from 15:18 UTC to 15:28 UTC. Customers can experience high DNS failures from within VPC during those two timeframes. We are investigating on the root cause. Everything is back to normal.

Report: "[GAPI] [fr-par-1] Generative APIs is down"

Last update
resolved

This incident has been resolved.

investigating

Since 1:08AM UTC Generative APIs encounter disruption of service. We are actively investigating the issue.

Report: "[SECRET MANAGER][FR-PAR] - Errors in secret creation"

Last update
resolved

This incident has been resolved.

monitoring

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

investigating

Since around 3:15PM UTC, secret versions cannot be created in the FR-PAR Secret Manager. We are investigating the issue.

Report: "[ELASTIC-METAL] - Rack A30 / Room 7 / DC5 - Device rebooted"

Last update
resolved

EM unreachable from 2025-05-16 05:07 UTC to 05:11 UTC (4 minutes). The associated network device rebooted unexpectedly.

Report: "[DC2] Rack H22 block N, block F unreachable."

Last update
resolved

This incident has been resolved.

identified

PSU issues on rack h22 block F and block N. Some servers may be unreachable. Replacement are in progress.

identified

RPN service is down on Rack H22 block F.

investigating

DC2 rack H22 block N, block F unreachable since 11:25 CEST. Analysis in progress.

Report: "[DC3] - Private switch issue in DC3 Room 4-3 : s43-d20.rpn.dc3"

Last update
resolved

This incident has been resolved.

monitoring

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

identified

We have detected a switch down in Room 4-3 : s43-d20.rpn.dc3. Servers in that rack currently have no <public/private> network access and are unreachable. 11.05.25 00h57 UTC Issue has been forwarded to our team for resolution.

Report: "[DC2] - Public switch issue in room 101 - s101-g27-13"

Last update
resolved

This incident has been resolved.

monitoring

We are continuing to monitor for any further issues.

monitoring

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

investigating

We have detected a switch down in room 101 - s101-g27-13. Servers in that rack currently have no public network access and are unreachable. 11.05.25 05h22 UTC Issue has been forwarded to our team for resolution.

Report: "[REDIS][FR-PAR1] Cluster issue"

Last update
resolved

The root cause was due to the VPC incident we encountered this morning. https://status.scaleway.com/incidents/nygwhbpk0sd4 During this time you may have encountered instability on your Redis clusters. Everything is back to normal. If you are still encountering an issue please open a ticket to our support team.

monitoring

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

investigating

Auto-healing workflows based on monitoring are triggered and rebooted some clusters.

Report: "[WEBHOSTING][ELEMENT] - Orders temporarily unavailable on Elements"

Last update
resolved

This incident has been resolved.

identified

Due to the migration of BookMyName, ordering Web Hosting is currently not possible on Elements. Thank you for your understanding.

Report: "[WEBHOSTING] - pf14-mysql & pf15-mysql are down."

Last update
resolved

This incident has been resolved.

monitoring

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

identified

The pf14-mysql is up and in monitoring.

identified

The pf14-mysql & pf15-mysql have been out of service since 8h15 AM. Our engineers are doing their utmost to restore the service as soon as possible.

Report: "[WEBHOSTING] - pf17-mysql is down."

Last update
resolved

This incident has been resolved.

monitoring

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

identified

The pf17-mysql have been out of service. Our engineers are doing their utmost to restore the service as soon as possible.

Report: "[Object Storage] - Checksum error in some client/sdk"

Last update
Investigating

S3 checksum error in some client/sdk, we alway return the full object checksum even when the request is ranged, causing issue in some high-level wrappers that try to compare the range's checksum with the full object one.Full integrity of the objects aren't impacted, and all computed checksum are valid.