- 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
-
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.
-
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 →
- Detected by Pingoru
- Aug 06, 2026, 08:43 AM UTC
- Resolved
- Aug 07, 2026, 12:47 PM UTC
- Duration
- 1d 4h
Affected: Cockpit
Timeline · 2 updates
-
investigating Aug 06, 2026, 08:43 AM UTC
Some customers cannot access Grafana. We are investigating.
-
resolved Aug 07, 2026, 12:47 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
resolved Aug 07, 2026, 12:47 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2026, 08:33 AM UTC
- Resolved
- Aug 06, 2026, 08:33 AM UTC
- Duration
- —
Affected: Cockpit
Timeline · 1 update
-
resolved Aug 06, 2026, 08:33 AM UTC
[05:00] Increase of query load broke store gateways.
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2026, 08:59 AM UTC
- Resolved
- Aug 07, 2026, 12:49 PM UTC
- Duration
- 2d 3h
Affected: DC3RPN
Timeline · 2 updates
-
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
-
resolved Aug 07, 2026, 12:49 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
investigating Aug 04, 2026, 04:24 PM UTC
We are continuing to investigate this issue.
-
monitoring Aug 04, 2026, 04:43 PM UTC
The incident has now been mitigated.
-
monitoring Aug 04, 2026, 04:45 PM UTC
We are continuing to monitor for any further issues.
-
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 →
- 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
-
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.
-
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 →
- 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
-
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 →
- 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
-
investigating Aug 03, 2026, 05:26 AM UTC
nomad allocations are failing - all pods cannot recover properly
-
resolved Aug 03, 2026, 07:42 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2026, 02:49 PM UTC
- Resolved
- Jul 31, 2026, 02:49 PM UTC
- Duration
- —
Affected: DediboxDC3
Timeline · 1 update
-
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 →
- 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
-
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
-
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.
-
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 →
- 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
-
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.
-
resolved Jul 29, 2026, 02:02 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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
-
resolved Jul 29, 2026, 09:07 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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
-
investigating Jul 28, 2026, 12:56 PM UTC
We are currently investigating this issue.
-
monitoring Jul 28, 2026, 01:18 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 28, 2026, 05:16 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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
-
monitoring Jul 28, 2026, 05:19 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 30, 2026, 08:58 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Jul 28, 2026, 10:16 AM UTC
For an unknown reason, half of rack E6 room 103 is down (PAR1- DC2)
-
investigating Jul 28, 2026, 12:33 PM UTC
We are continuing to investigate this issue.
-
investigating Jul 28, 2026, 12:43 PM UTC
We are continuing to investigate this issue.
-
resolved Jul 29, 2026, 01:42 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 28, 2026, 05:00 AM UTC
- Resolved
- Jul 28, 2026, 07:00 AM UTC
- Duration
- 2h
Timeline · 2 updates
Read the full incident report →
- 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
-
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
-
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
-
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 →
- 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
-
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.
-
resolved Jul 30, 2026, 08:43 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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)
-
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 →
- Detected by Pingoru
- Jul 23, 2026, 02:34 PM UTC
- Resolved
- Jul 23, 2026, 02:34 PM UTC
- Duration
- —
Affected: fr-par-1fr-par-2fr-par-3Kafka
Timeline · 1 update
-
resolved Jul 23, 2026, 02:34 PM UTC
[14:45] While upgrade our infra some of the clusters were unreachable
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2026, 12:57 PM UTC
- Resolved
- Jul 22, 2026, 12:57 PM UTC
- Duration
- —
Affected: Instances
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Jul 22, 2026, 09:33 AM UTC
- Resolved
- Jul 22, 2026, 09:55 AM UTC
- Duration
- 21m
Affected: Serverless Container
Timeline · 2 updates
Read the full incident report →
- 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
-
investigating Jul 21, 2026, 09:43 PM UTC
Product API is down for Kubernetes clusters
-
monitoring Jul 22, 2026, 01:40 AM UTC
The Kapsule public API is available again.
-
investigating Jul 22, 2026, 03:30 AM UTC
We are currently investigating this issue.
-
monitoring Jul 22, 2026, 03:52 AM UTC
The situation has returned to normal
-
resolved Jul 22, 2026, 04:56 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 09:03 PM UTC
- Resolved
- Jul 22, 2026, 04:55 AM UTC
- Duration
- 7h 52m
Affected: DatabasesInstancesKubernetes KapsuleServerless-Database
Timeline · 11 updates
Read the full incident report →