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 202644589 of 589 (100%)

Incidents, newest first

Notice August 17, 2026 [Serverless Containers] - [fr-par] - issues connecting to resources inside Private Network 20h 44m fr-par-1, fr-par-2, fr-par-3, Serverless Container

Started Aug 17, 2026, 04:41 PM UTC· resolved Aug 18, 2026, 01:26 PM UTC

  1. investigating Aug 17, 2026, 04:41 PM UTC

    On a small subset of our fr-par infrastructure, between 2026-08-17 09:20 UTC and 2026-08-17 16:15 UTC, some containers attached to a Private Network were not able to reach resources inside that PN. This issue is likely due to a faulty deployment, that we have reverted at 2026-08-17 16:15 UTC. Containers should now be able to reach resources in their Private Network as before. If your container has faced issues like "timeouts" or "connection error" while trying to reach a resource through their private endpoint during the time range above, the issues are likely linked. If you still continue to face these errors, feel free to open a support ticket. We sincerely apologize for any inconvenience.

  2. monitoring Aug 17, 2026, 04:48 PM UTC

    We have finished rolling back the faulty deployment. Situation should be good now for all users.

  3. resolved Aug 18, 2026, 01:26 PM UTC

    After investigation, we have found the root cause. The issue happened because of blackholed traffic, but only on some Private Networks with a specific configuration: - PNs with ACLs - PNs inside VPCs with "enable_routing" set to false Anyway, we have rolled back the component causing the issues, so this error shouldn't happen anymore. Sorry again for any inconvenience.

Read the full incident report →

Notice August 17, 2026 [VPCL] - [WAW2] - Some Instances were not reachable using VPC on PL-WAW-2 – Instances, VPC

Started Aug 17, 2026, 02:08 PM UTC· resolved Aug 17, 2026, 02:08 PM UTC

  1. resolved Aug 17, 2026, 02:08 PM UTC

    Customers may have experienced connectivity issues affecting some instances in the PL-WAW-2 region, preventing access via VPC. The issue was caused by a misconfiguration applied to an internal component. A fix was applied, and connectivity has been restored.

Read the full incident report →

Minor August 14, 2026 [EDGE] - random 403 returned on 76 pipelines 1h 31m Edge service

Started Aug 14, 2026, 12:49 PM UTC· resolved Aug 14, 2026, 02:20 PM UTC

  1. investigating Aug 14, 2026, 12:49 PM UTC

    403 errors may be returned for several pipelines, due to cache synchronization issue

  2. resolved Aug 14, 2026, 02:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 13, 2026 [PAR] Nine IX blackholed some traffic 4d 22h Dedibox, DC1, DC2, DC3 and 2 more

Started Aug 13, 2026, 04:30 PM UTC· resolved Aug 18, 2026, 03:29 PM UTC

  1. investigating Aug 13, 2026, 04:30 PM UTC

    While putting in production a new IXP, they forgot to update the ACL on their side but we were still able to reach the RS, so we announced our prefixes but the other members of the IXP weren’t able to send traffic to us, leading to blackhole of 20Gbps.

  2. resolved Aug 18, 2026, 03:29 PM UTC

    We are pleased to inform you that the issue has been resolved.

Read the full incident report →

Critical August 13, 2026 [Security vendor] - Suspicion of ESET blacklist for our domains and/or IP ranges 2h 37m Domains

Started Aug 13, 2026, 01:28 PM UTC· resolved Aug 13, 2026, 04:05 PM UTC

  1. identified Aug 13, 2026, 01:28 PM UTC

    Scaleway Security team identified that resources behind *.fr-par.scw.cloud may be blacklisted by the security vendor ESET. Scaleway is in discussion with ESET to remediate the situation as soon as possible.

  2. identified Aug 13, 2026, 01:38 PM UTC

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

  3. resolved Aug 13, 2026, 04:05 PM UTC

    The ESET has removed the domain from their blacklist.

Read the full incident report →

Minor August 13, 2026 [BMNA] - AFNIC EPP connection 23h 51m BookMyName

Started Aug 13, 2026, 09:08 AM UTC· resolved Aug 14, 2026, 08:59 AM UTC

  1. investigating Aug 13, 2026, 09:08 AM UTC

    Since 10:10 AM, our communication with AFNIC registry for TLDs (.fr, .bzh, .alsace, .paris, .wf, .yt, .tf, .pm) is unstable. Operations on domains from AFNIC may get errors. We are working on identifying the problem.

  2. resolved Aug 14, 2026, 08:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 12, 2026 Maintenance of one of the core routers in the AMS region. 11m AMS

Started Aug 12, 2026, 10:19 AM UTC· resolved Aug 12, 2026, 10:30 AM UTC

  1. investigating Aug 12, 2026, 10:19 AM UTC

    One of the two main routers will be taken out of service. During this period, the network connection will not be redundant in all availability zones of the region "The Netherlands - Amsterdam". No packet loss or latency changes are expected.

Read the full incident report →

Minor August 12, 2026 [EDGE] - 503 error 6d 7h Edge service

Started Aug 12, 2026, 08:00 AM UTC· resolved Aug 18, 2026, 03:41 PM UTC

  1. investigating Aug 12, 2026, 08:00 AM UTC

    Customer may experience 503 errors on edge service.

  2. identified Aug 12, 2026, 09:34 AM UTC

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

  3. resolved Aug 18, 2026, 03:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 11, 2026 [CKPT] - [Global] - On new projects, first attempts to connect to Grafana may result in internal error (the following ones end up working) 27d 6h Cockpit

Started Aug 11, 2026, 12:42 PM UTC· resolved Sep 07, 2026, 06:44 PM UTC

  1. investigating Aug 11, 2026, 12:42 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 07, 2026, 06:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 11, 2026 [FR-PAR] Serverless Databases issue 7d 7h Serverless-Database

Started Aug 11, 2026, 07:54 AM UTC· resolved Aug 18, 2026, 03:46 PM UTC

  1. monitoring Aug 11, 2026, 07:54 AM UTC

    Customer databases were unavailable between 8.54 am and 9.26 am. Our team had already fix but still monitoring this issue.

  2. resolved Aug 18, 2026, 03:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 6, 2026 [OBJS] - [PL-WAW] - Elevated p99 latencies due to some servers being down – pl-waw-1, pl-waw-2, pl-waw-3, Object Storage

Started Aug 06, 2026, 05:11 PM UTC· resolved Aug 06, 2026, 05:11 PM UTC

  1. identified Aug 06, 2026, 05:11 PM UTC

    August 5: From 2 p.m. to 6:30 p.m. CEST: Due to complications during scheduled hardware maintenance, some object storage servers were temporarily offline. During this period, customers may have experienced higher p99 latencies. Service availability was otherwise maintained.

  2. resolved Aug 06, 2026, 05:11 PM UTC

    The servers have been put back into production and latencies are now nominal.

Read the full incident report →

Minor August 6, 2026 [CKPT] - [global] - Grafana is partially unavailable 1d 4h Cockpit

Started Aug 06, 2026, 08:43 AM UTC· resolved Aug 07, 2026, 12:47 PM UTC

  1. investigating Aug 06, 2026, 08:43 AM UTC

    Some customers cannot access Grafana. We are investigating.

  2. resolved Aug 07, 2026, 12:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 6, 2026 [PGW] - [fr-par-1] - Public Gateway stuck in transient state 1d 4h Public Gateway

Started Aug 06, 2026, 08:39 AM UTC· resolved Aug 07, 2026, 12:47 PM UTC

  1. monitoring Aug 06, 2026, 08:39 AM UTC

    We have identified that the product Public Gateway creation/update in fr-par-1 were stuck in a transient state. The incident has been mitigated.

  2. resolved Aug 07, 2026, 12:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 6, 2026 [CKPT] - [fr-par] - Impossible to query metrics older than 12h – Cockpit

Started Aug 06, 2026, 08:33 AM UTC· resolved Aug 06, 2026, 08:33 AM UTC

  1. resolved Aug 06, 2026, 08:33 AM UTC

    [05:00] Increase of query load broke store gateways.

Read the full incident report →

Minor August 5, 2026 [NETI] - [DC3] - Dedibox RPN switch in DC3 (room 4-3, rack C9) is down 2d 3h DC3, RPN

Started Aug 05, 2026, 08:59 AM UTC· resolved Aug 07, 2026, 12:49 PM UTC

  1. investigating Aug 05, 2026, 08:59 AM UTC

    Switch s43-c9.rpn.dc3 is down. There is no RPN connection for the servers in DC3, room 4-3, rack C9

  2. resolved Aug 07, 2026, 12:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 4, 2026 [fr-par] Performance degradation affecting Block Storage 23h 33m fr-par-1, Databases, Instances, Object Storage and 1 more

Started Aug 04, 2026, 04:06 PM UTC· resolved Aug 05, 2026, 03:39 PM UTC

  1. investigating Aug 04, 2026, 04:06 PM UTC

    We are currently experiencing performance degradation on our Block Storage in the PAR1 region. Certain dependent services may be impacted, including Transactional Email and Managed Relational Databases.

  2. investigating Aug 04, 2026, 04:24 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Aug 04, 2026, 04:43 PM UTC

    The incident has now been mitigated.

  4. monitoring Aug 04, 2026, 04:45 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Aug 05, 2026, 03:39 PM UTC

    Everything has been stable again since 18:28 UTC. yesterday. The incident is closed.

Read the full incident report →

Minor August 4, 2026 [DC2] Public switch issue in DC2 room 205 rack E1 6h 5m Dedibox, DC2

Started Aug 04, 2026, 10:58 AM UTC· resolved Aug 04, 2026, 05:04 PM UTC

  1. identified Aug 04, 2026, 10:58 AM UTC

    We have detected a switch down in DC2 room 205 rack E1 Servers in that rack currently have no public network access and are unreachable.

  2. resolved Aug 04, 2026, 05:04 PM UTC

    This incident has been resolved, and all servers should now be reachable.

Read the full incident report →

Notice August 4, 2026 [WebHosting Elements] - pf-014 platform HTTP errors – Web Hosting

Started Aug 04, 2026, 09:18 AM UTC· resolved Aug 04, 2026, 09:18 AM UTC

  1. resolved Aug 04, 2026, 09:18 AM UTC

    Between approximately 15:00 and 15:45 CEST on 3 August, a Web Hosting platofrm pf-014 in fr-par experienced intermittent unavailability, resulting in HTTP errors and slow responses for websites hosted on it. Other servers in the Web Hosting fleet were unaffected. The cause was identified and has been corrected. The server remains under close monitoring.

Read the full incident report →

Minor August 3, 2026 [fr-par-1] - Unable to execute actions on Instances 2h 15m fr-par-1, Instances

Started Aug 03, 2026, 05:26 AM UTC· resolved Aug 03, 2026, 07:42 AM UTC

  1. investigating Aug 03, 2026, 05:26 AM UTC

    nomad allocations are failing - all pods cannot recover properly

  2. resolved Aug 03, 2026, 07:42 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 31, 2026 P4 - [NETI] - PARDC3 - Public switch s45-d14.dc3 rebooted – Dedibox, DC3

Started Jul 31, 2026, 02:49 PM UTC· resolved Jul 31, 2026, 02:49 PM UTC

  1. resolved Jul 31, 2026, 02:49 PM UTC

    At 15h55, public switch s45-d14.dc3 has rebooted; public network connectivity was affected for 10 minutes for all servers attached to it.

Read the full incident report →

Minor July 29, 2026 [TREM] - Service down 8h 12m Transactional Email

Started Jul 29, 2026, 03:15 PM UTC· resolved Jul 29, 2026, 11:28 PM UTC

  1. investigating Jul 29, 2026, 03:15 PM UTC

    Some instability and a down of the service, our team is in investigation to resolve the issue

  2. monitoring Jul 29, 2026, 03:31 PM UTC

    Service up again, but could suffer from latency, we are monitoring the situation. Unfortunately, the webhook event data history are currently lost.

  3. resolved Jul 29, 2026, 11:28 PM UTC

    The Transactional Email services have been running without any issue for a few hours, and we were able to partially retrieve webhook events for the last 15 days. Webhooks sent from 2026-07-29 13:10:28.678436+02 to 2026-07-29 17:23:09 UTC are definitively lost. To prevent further issues, the new webhook events retention has been lowered to 15 days.

Read the full incident report →

Minor July 29, 2026 [BRMI] - nl-ams-2 - no ssh access to server 20m nl-ams-2

Started Jul 29, 2026, 01:41 PM UTC· resolved Jul 29, 2026, 02:02 PM UTC

  1. investigating Jul 29, 2026, 01:41 PM UTC

    Installations may result in errors, and changing to rescue mode may fail in the NL-AMS-2 region specifically. We are currently investigating the issue.

  2. resolved Jul 29, 2026, 02:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 29, 2026 [TEM] - Service Down 9s Transactional Email

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

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

    Our service TEM has been down since 10:20 CEST It was resolved at 10:52 CEST

  2. resolved Jul 29, 2026, 09:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 28, 2026 [it-mil-1] - Multiple products not available 4h 41m VPC, it-mil-1

Started Jul 28, 2026, 12:35 PM UTC· resolved Jul 28, 2026, 05:16 PM UTC

  1. identified Jul 28, 2026, 12:35 PM UTC

    Multiple products unavailable since 13:50 CEST annotation audit trail cockpit containers datalab datawarehouse instance v1 k8s kafka kms mongo registry secrets

  2. investigating Jul 28, 2026, 12:56 PM UTC

    We are currently investigating this issue.

  3. monitoring Jul 28, 2026, 01:18 PM UTC

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

  4. resolved Jul 28, 2026, 05:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 28, 2026 [GAPI] - Gemma-4 infinite loops in response instabilities 1d 20h Generative API

Started Jul 28, 2026, 12:31 PM UTC· resolved Jul 30, 2026, 08:58 AM UTC

  1. investigating Jul 28, 2026, 12:31 PM UTC

    Users might experiment infinite loops in responses in case of multi turn tool_call requests using model gemma-4-26b-a4b-it

  2. monitoring Jul 28, 2026, 05:19 PM UTC

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

  3. resolved Jul 30, 2026, 08:58 AM UTC

    This incident has been resolved.

Read the full incident report →