Vendor reports: degradedResolved · vendor status “resolved”Official status API

[fr-par-1] Latencies spikes during the day following capacity increase in one of block storage cluster

Reported by Scaleway · Cloud & Infrastructure · source last read 5 min ago

Official source (opens in a new tab)
Vendor start
Oct 29, 2026, 11:01 UTC
Vendor's clock
Resolved
Nov 5, 2026, 14:35 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
7 d 3 h
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Scaleway reports degraded: "[fr-par-1] Latencies spikes during the day following capacity increase in one of block storage cluster".[E1, E2]
  • The vendor marked it resolved at 2026-11-05 14:35 UTC.[E3, E7]

Affected products and regions

  • Components: Block Storage, Databases, Instances.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-05 14:35 UTC · summary s1, evidence 285145f126d1d434

Evidence (7)
  1. E1Scaleway reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "[fr-par-1] Latencies spikes during the day following capacity increase in one of block storage cluster". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-10-29 11:01 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Block Storage, Databases, Instances. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-11-05 14:35 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Block Storage, Databases, Instances

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Scaleway is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Oct 29, 2026, 11:01 UTCVendor-reported startVendor time
  2. Nov 5, 2026, 14:35 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.