Scaleway Outage History

Scaleway degraded View live status →

Scaleway had 235 outages in the last 2 years totaling 388h 48m of downtime — averaging 9.7 incidents per month.

There were 235 Scaleway outages since July 16, 2025 totaling 388h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.scaleway.com

Minor August 6, 2026

[OBJS] - [PL-WAW] - Elevated p99 latencies due to some servers being down

Detected by Pingoru
Aug 06, 2026, 05:11 PM UTC
Resolved
Aug 06, 2026, 05:11 PM UTC
Duration
—
Affected: pl-waw-1pl-waw-2pl-waw-3Object Storage
Timeline · 2 updates
  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

[PGW] - [fr-par-1] - Public Gateway stuck in transient state

Detected by Pingoru
Aug 06, 2026, 08:39 AM UTC
Resolved
Aug 07, 2026, 12:47 PM UTC
Duration
1d 4h
Affected: Public Gateway
Timeline · 2 updates
  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 →

Major August 4, 2026

[fr-par] Performance degradation affecting Block Storage

Detected by Pingoru
Aug 04, 2026, 04:06 PM UTC
Resolved
Aug 05, 2026, 03:39 PM UTC
Duration
23h 33m
Affected: fr-par-1DatabasesInstancesObject StorageTransactional Email
Timeline · 5 updates
  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

Detected by Pingoru
Aug 04, 2026, 10:58 AM UTC
Resolved
Aug 04, 2026, 05:04 PM UTC
Duration
6h 5m
Affected: DediboxDC2
Timeline · 2 updates
  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

Detected by Pingoru
Aug 04, 2026, 09:18 AM UTC
Resolved
Aug 04, 2026, 09:18 AM UTC
Duration
—
Affected: Web Hosting
Timeline · 1 update
  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

Detected by Pingoru
Aug 03, 2026, 05:26 AM UTC
Resolved
Aug 03, 2026, 07:42 AM UTC
Duration
2h 15m
Affected: fr-par-1Instances
Timeline · 2 updates
  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 →

Minor July 29, 2026

[TREM] - Service down

Detected by Pingoru
Jul 29, 2026, 03:15 PM UTC
Resolved
Jul 29, 2026, 11:28 PM UTC
Duration
8h 12m
Affected: Transactional Email
Timeline · 3 updates
  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

Detected by Pingoru
Jul 29, 2026, 01:41 PM UTC
Resolved
Jul 29, 2026, 02:02 PM UTC
Duration
20m
Affected: nl-ams-2
Timeline · 2 updates
  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

Detected by Pingoru
Jul 29, 2026, 09:07 AM UTC
Resolved
Jul 29, 2026, 09:07 AM UTC
Duration
9s
Affected: Transactional Email
Timeline · 2 updates
  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

Detected by Pingoru
Jul 28, 2026, 12:35 PM UTC
Resolved
Jul 28, 2026, 05:16 PM UTC
Duration
4h 41m
Affected: VPCit-mil-1
Timeline · 4 updates
  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

Detected by Pingoru
Jul 28, 2026, 12:31 PM UTC
Resolved
Jul 30, 2026, 08:58 AM UTC
Duration
1d 20h
Affected: Generative API
Timeline · 3 updates
  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 →

Notice July 28, 2026

[EM] [DDX] (PAR-1 DC2) Some servers are down on rack E6 room 103

Detected by Pingoru
Jul 28, 2026, 10:16 AM UTC
Resolved
Jul 29, 2026, 01:42 PM UTC
Duration
1d 3h
Affected: DediboxDC2Elastic MetalServerless-Database
Timeline · 4 updates
  1. investigating Jul 28, 2026, 10:16 AM UTC

    For an unknown reason, half of rack E6 room 103 is down (PAR1- DC2)

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

    We are continuing to investigate this issue.

  3. investigating Jul 28, 2026, 12:43 PM UTC

    We are continuing to investigate this issue.

  4. resolved Jul 29, 2026, 01:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 24, 2026

[DEDIBOX] [DC2]- 1 rack lost public connectivity

Detected by Pingoru
Jul 24, 2026, 08:46 AM UTC
Resolved
Jul 24, 2026, 10:12 AM UTC
Duration
1h 25m
Affected: DediboxDC2
Timeline · 3 updates
  1. investigating Jul 24, 2026, 08:46 AM UTC

    Due to a network equipment failure, Dedibox servers in the following racks at the OPCORE datacenter are affected: - s202A-B7

  2. investigating Jul 24, 2026, 08:50 AM UTC

    Due to a network equipment failure, Dedibox servers in the following racks at the OPCORE datacenter are affected: - s202A-B7

  3. resolved Jul 24, 2026, 10:12 AM UTC

    The faulty switch has been replaced. Every server should now be reachable.

Read the full incident report →

Minor July 24, 2026

[BMNA] - Certificate imap.bookmyname.com seems to be incorrect

Detected by Pingoru
Jul 24, 2026, 08:32 AM UTC
Resolved
Jul 30, 2026, 08:43 AM UTC
Duration
6d
Affected: BookMyName
Timeline · 2 updates
  1. investigating Jul 24, 2026, 08:32 AM UTC

    We are currently investigating an issue with the SSL certificates on imap.bookmyname.com and smtp.bookmyname.com. This issue may prevent some users from sending or receiving emails through these endpoints.

  2. resolved Jul 30, 2026, 08:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 23, 2026

[API Gateway] - [it-mil] - connection failures

Detected by Pingoru
Jul 23, 2026, 02:41 PM UTC
Resolved
Jul 23, 2026, 03:23 PM UTC
Duration
42m
Affected: APIs
Timeline · 2 updates
  1. identified Jul 23, 2026, 02:41 PM UTC

    Since around 1 PM UTC, some internal connections to Scaleway API on it-mil region started to fail. As a result: -Pushes to rg.it-mil.scw.eu are failing with HTTP 500 -Serverless Containers deployments are failing (resources stuck in creating) -etc. (list is not exhaustive)

  2. resolved Jul 23, 2026, 03:23 PM UTC

    The situation has been back to normal since 3:15 PM. Pushes to the registry and container deployments in the IT-mil region are working again. Sorry about any inconvenience.

Read the full incident report →

Notice July 22, 2026

[JOBS] - [fr-par] - Execution of some job runs was interrupted

Detected by Pingoru
Jul 22, 2026, 12:57 PM UTC
Resolved
Jul 22, 2026, 12:57 PM UTC
Duration
—
Affected: Instances
Timeline · 1 update
  1. resolved Jul 22, 2026, 12:57 PM UTC

    During compute instances incident on fr-par (cf. this status: https://status.scaleway.com/incidents/bsp2y5fysy9w), some jobs were interrupted during execution or were not executed at all. They ended in an Interrupted state with a reason technical_error. This happened intermittantly and only form some job runs only between 21/07/2026 22:00:00 CEST and 22/07/2026 01:49:00 CEST and between 22/07/2026 03:44:00 CEST and 21/07/2026 05:30:00. The number of impacted job runs represent approximately the tenth of our average daily job runs. This is an informative status and no corrective action was required by us. Please check if you need to run your job again. We apologize for the inconvenience.

Read the full incident report →

Major July 21, 2026

[KUBERNETES] - [fr-par] - Product API down

Detected by Pingoru
Jul 21, 2026, 09:43 PM UTC
Resolved
Jul 22, 2026, 04:56 AM UTC
Duration
7h 12m
Affected: Kubernetes Kapsule
Timeline · 5 updates
  1. investigating Jul 21, 2026, 09:43 PM UTC

    Product API is down for Kubernetes clusters

  2. monitoring Jul 22, 2026, 01:40 AM UTC

    The Kapsule public API is available again.

  3. investigating Jul 22, 2026, 03:30 AM UTC

    We are currently investigating this issue.

  4. monitoring Jul 22, 2026, 03:52 AM UTC

    The situation has returned to normal

  5. resolved Jul 22, 2026, 04:56 AM UTC

    This incident has been resolved.

Read the full incident report →