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 202644593 of 593 (100%)

Incidents, newest first

Minor July 10, 2026 [Managed Inference] - [fr-par] Increase duration of deployment creation time 2h 11m Managed Inference

Started Jul 10, 2026, 06:59 AM UTC· resolved Jul 10, 2026, 09:10 AM UTC

  1. investigating Jul 10, 2026, 06:59 AM UTC

    Customers may experience longer deployment creation times on Managed Inference in fr-par

  2. resolved Jul 10, 2026, 09:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 10, 2026 [Serverless Containers] - [nl-ams] Connectivity issues 4h 47m Load Balancer, Serverless Container

Started Jul 10, 2026, 05:57 AM UTC· resolved Jul 10, 2026, 10:45 AM UTC

  1. investigating Jul 10, 2026, 05:57 AM UTC

    Starting from 07:30 CET, users may experience connectivity issues or failed requests when accessing their Serverless Containers in the nl-ams region. This issue is under investigation by our team.

  2. monitoring Jul 10, 2026, 07:32 AM UTC

    Update: Connectivity has been partially restored at around 9:30 AM. We are monitoring the situation.

  3. resolved Jul 10, 2026, 10:45 AM UTC

    The connectivity issues affecting Serverless Containers in the nl‑ams region occurred between 07:40 CET and 09:30 CET. As of 09:30 CET, the service is stable and fully reachable. If you still experience any problems, please contact our Support team. Thank you for your patience.

Read the full incident report →

Minor July 9, 2026 [Generative APIs] - mistral-medium-3.5-128b might be unresponsive 16m Generative API

Started Jul 09, 2026, 04:19 PM UTC· resolved Jul 09, 2026, 04:36 PM UTC

  1. investigating Jul 09, 2026, 04:19 PM UTC

    Customers may experience unresponsiveness when using the mistral-medium-3.5-128b model due to an instability on an internal component.

  2. resolved Jul 09, 2026, 04:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 9, 2026 WebHosting Elements and WebHosting Dedibox 12m Hosting

Started Jul 09, 2026, 02:47 PM UTC· resolved Jul 09, 2026, 03:00 PM UTC

  1. investigating Jul 09, 2026, 02:47 PM UTC

    Maintenance for security system update. A downtime of 10 min can be expected during the maintenance Date/time: July 9th from 16h to 17h

  2. resolved Jul 09, 2026, 03:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 9, 2026 [Managed Datalab] - [fr-par] Spark cluster creation failures 17h 10m fr-par-1, fr-par-2, fr-par-3, Clusters for Apache Spark™

Started Jul 09, 2026, 02:35 PM UTC· resolved Jul 10, 2026, 07:45 AM UTC

  1. investigating Jul 09, 2026, 02:35 PM UTC

    Customers may experience failures when creating Spark clusters in the fr-par region due to an issue with an internal dependency.

  2. investigating Jul 10, 2026, 07:43 AM UTC

    We are continuing to investigate this issue.

  3. resolved Jul 10, 2026, 07:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 9, 2026 [BookMyName] - [world] - Timeouts on web interface and API 21m BookMyName, Domains

Started Jul 09, 2026, 08:29 AM UTC· resolved Jul 09, 2026, 08:51 AM UTC

  1. investigating Jul 09, 2026, 08:29 AM UTC

    Customers may experience timeouts when accessing the BookMyName web interface and API due to an internal component failure.

Read the full incident report →

Minor July 9, 2026 [Network infrastructure] - [DC2] - Public switch s301-b5-2 has rebooted – DC2

Started Jul 09, 2026, 08:06 AM UTC· resolved Jul 09, 2026, 08:06 AM UTC

  1. resolved Jul 09, 2026, 08:06 AM UTC

    Customers may experience a partial outage on public connectivity for a few minutes due to a reboot of the public switch s301-b5-2 in DC2.

Read the full incident report →

Major July 9, 2026 [Object Storage] - [it-mil-1] Object Storage connectivity issues 12d 17h Object Storage, Audit Trail

Started Jul 09, 2026, 07:37 AM UTC· resolved Jul 22, 2026, 01:32 AM UTC

  1. investigating Jul 09, 2026, 07:37 AM UTC

    Customers may experience connectivity issues with Object Storage on it-mil-1.

  2. investigating Jul 09, 2026, 08:03 AM UTC

    Since 08/07 16H UTC customers may experience connectivity issues with Object Storage on it-mil-1.

  3. investigating Jul 09, 2026, 08:25 AM UTC

    We are continuing to investigate this issue.

  4. investigating Jul 09, 2026, 08:26 AM UTC

    We are continuing to investigate this issue.

  5. investigating Jul 09, 2026, 08:35 AM UTC

    Since 08/07 15H11 UTC Object storage customers experienced connectivity issues with Object Storage on it-mil-1. This was a routing issue and a fix was implemented at 08H26 UTC. Situation is back to normal.

  6. monitoring Jul 09, 2026, 08:35 AM UTC

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

  7. resolved Jul 22, 2026, 01:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 9, 2026 [Edge Services] - [world] High amount of 503 on pipeline with Object storage backend –

Started Jul 09, 2026, 07:00 AM UTC· resolved Jul 09, 2026, 07:00 AM UTC

  1. resolved Jul 09, 2026, 09:29 AM UTC

    Today, between 9:12 AM and 10:15 AM (Paris time), customers experienced a high number of HTTP 503 errors on Edge Services pipelines with Object Storage backends due to DNS resolution issues affecting an internal component. This incident has now been resolved, and our teams are continuing to monitor the situation.

Read the full incident report →

Minor July 8, 2026 [MSGQ] - [fr-par] Missing IPs quotas on Production organisation 4h 37m Excellence

Started Jul 08, 2026, 05:07 PM UTC· resolved Jul 08, 2026, 09:45 PM UTC

  1. investigating Jul 08, 2026, 05:07 PM UTC

    Customers may be unable to create new deployments due to a lack of available IP addresses on the MSGQ service in the fr-par region.

  2. resolved Jul 08, 2026, 09:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 [Scaleblocks] - [fr-par] SEDB deployment creation failures 3h 2m Block Storage

Started Jul 08, 2026, 01:48 PM UTC· resolved Jul 08, 2026, 04:51 PM UTC

  1. investigating Jul 08, 2026, 01:48 PM UTC

    Customers may experience failures when creating SEDB deployments due to a certificate-related error on an internal dependency.

  2. resolved Jul 08, 2026, 04:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 [Object Storage] - [it-mil-1] Routing issue causing service unavailability 17h 58m Object Storage

Started Jul 08, 2026, 12:33 PM UTC· resolved Jul 09, 2026, 06:31 AM UTC

  1. investigating Jul 08, 2026, 12:33 PM UTC

    Customers may experience service unavailability on Object Storage in it-mil-1 due to a routing issue.

  2. resolved Jul 09, 2026, 06:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 8, 2026 [Network infrastructure] - [nl-ams-1] Public switch reboot room H6-6B60 – AMS

Started Jul 08, 2026, 10:20 AM UTC· resolved Jul 08, 2026, 10:20 AM UTC

  1. resolved Jul 08, 2026, 10:20 AM UTC

    Customers may have experienced a partial outage of public connectivity on servers attached to the public switch h6-6b60-6.ams1 in the AMS1 region.

Read the full incident report →

Minor July 8, 2026 [BareMetal Provisionner] - [nl-ams] iPXE boot failures 6h 37m Elastic Metal

Started Jul 08, 2026, 09:23 AM UTC· resolved Jul 08, 2026, 04:01 PM UTC

  1. investigating Jul 08, 2026, 09:23 AM UTC

    Servers continue to operate normally. However, customers may experience failures when attempting to reboot servers in rescue mode or perform install, reinstall, clean, and reset operations due to an incompatibility with an internal dependency.

  2. monitoring Jul 08, 2026, 10:48 AM UTC

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

  3. resolved Jul 08, 2026, 04:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 7, 2026 [File Storage] - [fr-par-1] High latencies on File Storage 1d Block Storage

Started Jul 07, 2026, 10:24 AM UTC· resolved Jul 08, 2026, 10:46 AM UTC

  1. investigating Jul 07, 2026, 10:24 AM UTC

    Customers may experience high latencies on File Storage in fr-par-1, we are currently investigating this issue.

  2. resolved Jul 08, 2026, 10:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 7, 2026 [MongoDB] - [fr-par] Unable to restore snapshots on previously restored instances 3d 4h Databases

Started Jul 07, 2026, 09:04 AM UTC· resolved Jul 10, 2026, 01:32 PM UTC

  1. investigating Jul 07, 2026, 09:04 AM UTC

    Instances that were restored through snapshots can produce new snapshots, but cannot restore those snapshots. We are currently investigating this issue.

  2. identified Jul 08, 2026, 12:06 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jul 10, 2026, 01:32 PM UTC

    Les nouvelles instances restaurées ne seront pas impactées par ce problème. Les clients concernés par l'indisponibilité de leurs snapshots seront contactés individuellement afin d'être informés de la maintenance corrective.

Read the full incident report →

Minor July 7, 2026 [Public Gateway] - [nl-ams-1] Unable to create or upgrade new gateways 2h 48m Network

Started Jul 07, 2026, 07:07 AM UTC· resolved Jul 07, 2026, 09:55 AM UTC

  1. investigating Jul 07, 2026, 07:07 AM UTC

    We are currently experiencing an issue in the ams1 zone affecting the creation and upgrading of Public Gateways. Existing online gateways are not affected. Our engineering team is actively investigating, and we will provide updates as they become available.

  2. monitoring Jul 07, 2026, 07:15 AM UTC

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

  3. resolved Jul 07, 2026, 09:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 7, 2026 [File Storage] - [fr-par-1] High latencies 3h 36m fr-par-1, File Storage

Started Jul 07, 2026, 01:55 AM UTC· resolved Jul 07, 2026, 05:31 AM UTC

  1. investigating Jul 07, 2026, 01:55 AM UTC

    Customers may experience high latencies on File Storage in fr-par-1 due to an internal component issue.

  2. monitoring Jul 07, 2026, 02:18 AM UTC

    Customers may experience high latencies on File Storage in fr-par-1 due to an internal component issue. The issue has been identified and resolved. We are monitoring the situation to ensure stability.

  3. resolved Jul 07, 2026, 05:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 6, 2026 [Billing] - Duplicate email sent for Purchase Orders 21h 35m Billing

Started Jul 06, 2026, 11:36 AM UTC· resolved Jul 07, 2026, 09:12 AM UTC

  1. investigating Jul 06, 2026, 11:36 AM UTC

    Customers may receive duplicate email notifications for their purchase orders.

  2. monitoring Jul 06, 2026, 04:19 PM UTC

    The issue has been found and fixed. Duplicate billing emails were sent, especially during the domain direct purchase. Actual charges were processed only once.

  3. resolved Jul 07, 2026, 09:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 6, 2026 [Network infrastructure] - [nl-ams] Public switch h6-1219 is unreachable 1h 51m AMS

Started Jul 06, 2026, 07:32 AM UTC· resolved Jul 06, 2026, 09:23 AM UTC

  1. investigating Jul 06, 2026, 07:32 AM UTC

    Customers experience a full outage of public connectivity on servers located in Hall 6, rack 6.12.19, ams1.

  2. resolved Jul 06, 2026, 09:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 4, 2026 [Block Storage] - [fr-par-2] High latencies on b_ssd volumes 1d 14h Block Storage

Started Jul 04, 2026, 07:35 PM UTC· resolved Jul 06, 2026, 09:46 AM UTC

  1. monitoring Jul 04, 2026, 07:35 PM UTC

    Customers using b_ssd volume experienced high latencies from 18h25 to 18h30 UTC due to a network issue. sbs_5k and sbs_15k were NOT impacted.

  2. resolved Jul 06, 2026, 09:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 4, 2026 [Block Storage] - [fr-par-2] High latencies and errors on volumes 1h 56m Block Storage

Started Jul 04, 2026, 07:23 PM UTC· resolved Jul 04, 2026, 09:20 PM UTC

  1. investigating Jul 04, 2026, 07:23 PM UTC

    Customers may experience high latencies and errors on Block Storage volumes in fr-par-2 due to an issue on an internal component.

  2. resolved Jul 04, 2026, 09:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 3, 2026 [Generative APIs] - qwen3.6-35b-a3b model instabilities 6d 3h Generative API

Started Jul 03, 2026, 10:21 AM UTC· resolved Jul 09, 2026, 01:28 PM UTC

  1. investigating Jul 03, 2026, 10:21 AM UTC

    Customers may experience transient 5xx errors when using the qwen3.6-35b-a3b model due to instabilities on an internal component.

  2. resolved Jul 09, 2026, 01:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 2, 2026 [Environmental Footprint Usage] - flaky behavior on environmental impact availability report and environmental dashboard – Environmental Footprint

Started Jul 02, 2026, 10:30 AM UTC· resolved Jul 02, 2026, 10:30 AM UTC

  1. resolved Jul 02, 2026, 10:30 AM UTC

    Customers may experience flaky behavior on the Environmental Impact Availability Report and Environmental Dashboard due to an internal dependency.

Read the full incident report →

Minor July 2, 2026 [Dedibox VPS] - VPS connectivity issues in Paris. 23h 18m Dedibox VPS

Started Jul 02, 2026, 08:28 AM UTC· resolved Jul 03, 2026, 07:47 AM UTC

  1. investigating Jul 02, 2026, 08:28 AM UTC

    Customers may experience connectivity issues with their Dedibox VPS instances in the Paris region due to an internal infrastructure issue.

  2. resolved Jul 03, 2026, 07:47 AM UTC

    Customers may have experienced connectivity issues with their Dedibox VPS instances in the Paris region due to an internal infrastructure issue. The issue has been resolved and all services are now operating normally.

Read the full incident report →