Scaleway Outage History

Scaleway degraded · 4 active incidents · 2 long-running issues View live status →

Pingoru has recorded 363 incidents for Scaleway: 362 in the last 12 months and 133 in the last 90 days.

Source: status.scaleway.com

363incidents recorded
362last 12 months
133last 90 days
3 daystypical duration
Incidents per month
050100AprMayJunJulAugSepOct44
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct100%
Pingoru began tracking Scaleway in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202636646 of 720 (90%)
May 202645723 of 744 (97%)
June 202660575 of 720 (80%)
July 202665654 of 744 (88%)
August 202634572 of 744 (77%)
September 202647720 of 720 (100%)
October 202644595 of 595 (100%)

Incidents, newest first

Notice April 15, 2026 [PGWY] - [fr-par-1] - Error 500 when booking a public Gateway – Public Gateway

Started Apr 15, 2026, 09:36 AM UTC· resolved Apr 15, 2026, 09:36 AM UTC

  1. resolved Apr 15, 2026, 09:36 AM UTC

    got a temporary api issue between 7:17 UTC to 8:25 UTC.

Read the full incident report →

Minor April 14, 2026 [Network infrastructure] - [DC2] Room 108 Rack A7 network issue 2h 6m Network

Started Apr 14, 2026, 09:23 AM UTC· resolved Apr 14, 2026, 11:30 AM UTC

  1. investigating Apr 14, 2026, 09:23 AM UTC

    Customers may experience network connectivity issues on Room 108 Rack A7 in DC2 due to a configuration error on an internal component.

  2. resolved Apr 14, 2026, 11:30 AM UTC

    The issue has been resolved and all services are now operating normally.

Read the full incident report →

Notice April 13, 2026 [BMNA] - [world] - BMN services down – BookMyName

Started Apr 13, 2026, 07:25 AM UTC· resolved Apr 13, 2026, 07:25 AM UTC

  1. resolved Apr 13, 2026, 07:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 11, 2026 [BLOCK STORAGE] - [fr-par] - High latencies on part of infrastructure 1d 23h Databases

Started Apr 11, 2026, 02:51 PM UTC· resolved Apr 13, 2026, 02:06 PM UTC

  1. investigating Apr 11, 2026, 02:51 PM UTC

    We are currently experiencing increased latencies on one of our clusters in the PAR-1 region, since 13:20 UTC. This situation may also impact other services relying on this infrastructure: Mongo DB, Postgresql DB, MySQL DB, Serverless, Data Warehouse, Cockpit, ServerlessDB. Our teams are actively working on. The situation has slightly improved since the beginning of the mitigation actions, and additional measures will be implemented shortly to further reduce the impact.

  2. investigating Apr 11, 2026, 04:22 PM UTC

    Block Storage issue is now corrected. We are still working on managing possible impacts on other products.

  3. monitoring Apr 11, 2026, 08:50 PM UTC

    All side effects have been managed. We continue to monitor the situation.

  4. resolved Apr 13, 2026, 02:06 PM UTC

    No more disruption since 48 hours. Returned to a plain healthy state. No dataloss detected on affected cluster.

Read the full incident report →

Minor April 9, 2026 [Data Warehouse] - fr-par - New S3 API keys not working 1h Serverless-Database

Started Apr 09, 2026, 02:50 PM UTC· resolved Apr 09, 2026, 03:50 PM UTC

  1. investigating Apr 09, 2026, 02:50 PM UTC

    Customers may experience access issues with newly generated S3 API keys due to insufficient bucket permissions. We are currently investigating the root cause.

  2. resolved Apr 09, 2026, 03:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 8, 2026 [Instance Orchestration] - [pl-waw] Instance orchestrations APIs may encounter failures 3h 47m Instances

Started Apr 08, 2026, 11:34 AM UTC· resolved Apr 08, 2026, 03:21 PM UTC

  1. identified Apr 08, 2026, 11:34 AM UTC

    Customers may experience issues with Instance Orchestration APIs due to an internal component failure during routine deployments. We are working on restoring the APIs as soon as possible.

  2. monitoring Apr 08, 2026, 11:50 AM UTC

    The issue has been identified and resolved, and we are monitoring the situation to ensure stability.

  3. resolved Apr 08, 2026, 03:21 PM UTC

    The issue has been identified and resolved, and we are monitoring the situation to ensure stability.

Read the full incident report →

Minor April 8, 2026 [Dedibackup] - DC3 - 500 errors on Dedibackup 1h 56m Dedibackup

Started Apr 08, 2026, 11:24 AM UTC· resolved Apr 08, 2026, 01:20 PM UTC

  1. investigating Apr 08, 2026, 11:24 AM UTC

    Some customers may experience 500 errors when trying to connect to Dedibackup in DC3.

  2. identified Apr 08, 2026, 01:18 PM UTC

    Some customers may experience 500 errors when trying to connect to Dedibackup in fr-par-1.

  3. resolved Apr 08, 2026, 01:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 7, 2026 [Container Registry] - [nl-ams]- High error rate on registry API 3h 45m Container Registry

Started Apr 07, 2026, 08:02 AM UTC· resolved Apr 07, 2026, 11:48 AM UTC

  1. investigating Apr 07, 2026, 08:02 AM UTC

    Customers may experience a high error rate on the Container Registry API.

  2. monitoring Apr 07, 2026, 08:46 AM UTC

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

  3. resolved Apr 07, 2026, 11:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 4, 2026 [DC5] Public switch issue in DC5 Room 1 1 Rack D39 4h 29m Dedibox, DC5

Started Apr 04, 2026, 05:41 PM UTC· resolved Apr 04, 2026, 10:10 PM UTC

  1. investigating Apr 04, 2026, 05:41 PM UTC

    We have detected that public switches were down in DC5 Room 1 1 Rack D39. Servers in that rack currently have no network access and are unreachable, RPN network is still reachable.

  2. identified Apr 04, 2026, 07:15 PM UTC

    The Switch is currently down and is being replaced.

  3. resolved Apr 04, 2026, 10:10 PM UTC

    Switch has been replaced network is up for the Rack D39

Read the full incident report →

Minor April 3, 2026 [DDBX]-Installation broken for windows 2019/2022 6h 34m Dedibox

Started Apr 03, 2026, 09:47 AM UTC· resolved Apr 03, 2026, 04:21 PM UTC

  1. investigating Apr 03, 2026, 09:47 AM UTC

    An incident is currently occurring on the Windows systems : - Windows 2019 Hyper-V - Windows 2019 Standard - Windows 2019 Datacenter - Windows 2022 Standard - Windows 2022 Datacenter We are currently investigating this issue.

  2. resolved Apr 03, 2026, 04:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 2, 2026 [PAYMENT] - Payment result handling issue 24d 18h Billing

Started Apr 02, 2026, 01:55 PM UTC· resolved Apr 27, 2026, 08:26 AM UTC

  1. investigating Apr 02, 2026, 01:55 PM UTC

    Some customers paying by card may experience a display issue where the invoice shows "unpaid" even though it has been paid. We apologize for any inconvenience this may cause.

  2. resolved Apr 27, 2026, 08:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 1, 2026 [TEM] Increase latency and timeout error for email ingestion – BookMyName, Databases, Transactional Email

Started Apr 01, 2026, 03:12 PM UTC· resolved Apr 01, 2026, 03:12 PM UTC

  1. resolved Apr 01, 2026, 03:12 PM UTC

    During a product maintenance, we have noticed an increase of latency and errors. Our team performed a rollback and monitor the situation since then. The instability was seen during approximately two hours (12h20 to 14h UTC).

Read the full incident report →

Minor April 1, 2026 [Cockpit] - SMTP alert manager mail is broken 6d 23h Observability

Started Apr 01, 2026, 08:44 AM UTC· resolved Apr 08, 2026, 07:56 AM UTC

  1. investigating Apr 01, 2026, 08:44 AM UTC

    The SMTP communication with TEM is currently disrupted due to a key rotation issue. This may affect the delivery of alert emails.

  2. resolved Apr 08, 2026, 07:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 31, 2026 [Webmail] [fr-par] Webmail unavailable on pf-012 7d 13h Web Hosting

Started Mar 31, 2026, 06:18 PM UTC· resolved Apr 08, 2026, 07:39 AM UTC

  1. investigating Mar 31, 2026, 06:18 PM UTC

    Webmail is not accessible for hostings on pf-012.whm.fr-par.scw.cloud

  2. monitoring Mar 31, 2026, 06:27 PM UTC

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

  3. resolved Apr 08, 2026, 07:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 31, 2026 [RPN-SAN] - [DC2/DC3] SAN cluster RAID disk failure 3d 3h SAN

Started Mar 31, 2026, 01:04 PM UTC· resolved Apr 03, 2026, 04:21 PM UTC

  1. investigating Mar 31, 2026, 01:04 PM UTC

    Between 23:45 and 01:30 on sunday, 4 disks failed on our SAN Cluster server, compromising the RAID configuration. We are attempting to recover data using a spare server.

  2. investigating Mar 31, 2026, 01:18 PM UTC

    We are continuing to investigate this issue.

  3. identified Apr 02, 2026, 12:27 PM UTC

    The RAID is currently being rebuilt. An operation to recover the service is underway. The service should be back tomorrow if everything goes smoothly.

  4. resolved Apr 03, 2026, 04:21 PM UTC

    The issue has been resolved. Please contact our support team if you have any issue with our SAN.

Read the full incident report →

Minor March 31, 2026 [WebHosting Elements] - [fr-par-2] IPV6 not working on pf-012.whm.fr-par.scw.cloud 4h 22m fr-par-2, Web Hosting

Started Mar 31, 2026, 09:19 AM UTC· resolved Mar 31, 2026, 01:42 PM UTC

  1. investigating Mar 31, 2026, 09:19 AM UTC

    IPV6 connectivity is currently unavailable. This may affect services relying on IPV6 addresses.

  2. identified Mar 31, 2026, 12:49 PM UTC

    IPV6 connectivity is currently unavailable on the platform pf-012.whm.fr-par.scw.cloud. This may affect services relying on IPV6 addresses. We have identified the cause and are working on a resolution.

  3. resolved Mar 31, 2026, 01:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 30, 2026 [Kapsule & Kosmos] - [FR-PAR] Cannot create cluster – fr-par-1, fr-par-2, fr-par-3, Kubernetes Kapsule

Started Mar 30, 2026, 03:45 PM UTC· resolved Mar 30, 2026, 03:45 PM UTC

  1. resolved Mar 30, 2026, 03:45 PM UTC

    Start from 30 march 2026 at 15h53 CET, Kapsule cluster creation was not possible. The incident was resolved 30 march 2026 at 17h04.

Read the full incident report →

Minor March 27, 2026 [Data Warehouse] - [fr-par] New deployment blocked 1h 27m fr-par-1, fr-par-2, fr-par-3, Data Warehouse

Started Mar 27, 2026, 11:17 AM UTC· resolved Mar 27, 2026, 12:45 PM UTC

  1. investigating Mar 27, 2026, 11:17 AM UTC

    New deployments cannot be created at this time. Starting existing deployments may also result in failure.

  2. resolved Mar 27, 2026, 12:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 27, 2026 [SERVERLESS CONTAINER][WAW][AMS] Serverless Containers were autonomously redeployed by the platform – nl-ams-1, nl-ams-2, nl-ams-3, pl-waw-1 and 3 more

Started Mar 27, 2026, 09:57 AM UTC· resolved Mar 27, 2026, 09:57 AM UTC

  1. resolved Mar 27, 2026, 09:57 AM UTC

    On March 26, 2026, we experienced an incident affecting Serverless Containers in the following regions: pl-waw: from approximately 11:30 CET to 11:36 CET nl-ams: from approximately 13:30 CET to 13:40 CET During these periods, a platform-level component triggered an automatic redeployment of active Serverless Containers. This action was initiated without any user intervention and was unintended. The sudden scaling activity caused temporary disruptions across the Serverless platform, including brief network connectivity issues—particularly for containers connected to VPC. Impact: - Brief service interruptions for running Serverless Containers - Transient network issues, especially for Serverless Containers configured with private networks - Increased startup latency during the redeployment window All systems are now operating normally, and no further action is required from users. We sincerely apologize for the disruption. Our team has identified the cause. No reoccurrence is expected to happen. We appreciate your understanding and patience.

Read the full incident report →

Notice March 26, 2026 [Audit Trail] - [fr-par] - API Partial Outage 10d 16h Secret Manager

Started Mar 26, 2026, 04:04 PM UTC· resolved Apr 06, 2026, 08:13 AM UTC

  1. investigating Mar 26, 2026, 04:04 PM UTC

    We are currently experiencing a partial outage affecting the Audit Trail API in the fr-par region. This may impact your ability to access or use the Audit Trail service. Customers may see 503 responses on some requests to the audit trail API, but no events are being lost.

  2. investigating Mar 26, 2026, 04:12 PM UTC

    The issue has been mitigated, and we are investigating its root cause.

  3. resolved Apr 06, 2026, 08:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 26, 2026 [cPanel Webhosting] Server Update –

Started Mar 26, 2026, 02:00 PM UTC· resolved Mar 26, 2026, 02:00 PM UTC

  1. resolved Mar 26, 2026, 02:35 PM UTC

    We have performed a server maintenance for the cPanel platform 1006. A downtime of 10 min may have occured during the maintenance.

Read the full incident report →

Minor March 26, 2026 [Network infrastructure] - DC5 Room 1 Rack B15 - RPN switch rebooted – fr-par-2, Block Storage, Elastic Metal, Object Storage

Started Mar 26, 2026, 10:57 AM UTC· resolved Mar 26, 2026, 10:57 AM UTC

  1. resolved Mar 26, 2026, 10:57 AM UTC

    At 02:25:50 UTC+1, an RPN switch in DC5 Room 1 Rack B15 rebooted, interrupting network traffic for servers attached to it for 10 minutes.

Read the full incident report →

Critical March 25, 2026 [MongoDB] - [fr-par-1] Connectivity Loss on Public Endpoint 21h 12m fr-par-1, Databases

Started Mar 25, 2026, 10:21 AM UTC· resolved Mar 26, 2026, 07:34 AM UTC

  1. investigating Mar 25, 2026, 10:21 AM UTC

    Customers are experiencing connectivity issues through public endpoints. The public endpoint IPs are not pointing to the new nodes.

  2. monitoring Mar 25, 2026, 11:51 AM UTC

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

  3. resolved Mar 26, 2026, 07:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 25, 2026 [AUDT] - [pl-waw] - NATS stream not responsive 37m pl-waw-1, pl-waw-2, pl-waw-3, IAM

Started Mar 25, 2026, 09:56 AM UTC· resolved Mar 25, 2026, 10:34 AM UTC

  1. investigating Mar 25, 2026, 09:56 AM UTC

    Events in PL-WAW are not being displayed in Audit Trail since 9:53 GMT+1. Those events are not lost because we have a backup solution that stores the events in case of incidents like this. We are actively working on fixing the issue.

  2. resolved Mar 25, 2026, 10:34 AM UTC

    The incident was resolved at 11:22 a.m. CET.

Read the full incident report →

Minor March 25, 2026 [Network infrastructure] [DC2] Public switch rebooted Room 103 - Rack: 9-2 32s DC2, Network

Started Mar 25, 2026, 09:46 AM UTC· resolved Mar 25, 2026, 09:46 AM UTC

  1. investigating Mar 25, 2026, 09:46 AM UTC

    At 21:01 UTC+1, a public switch in Room 103 - Rack: 9-2 rebooted, causing all servers in the affected rack to lose public connectivity until the switch came back online at 21:04.

  2. resolved Mar 25, 2026, 09:46 AM UTC

    This incident has been resolved.

Read the full incident report →