CHYP.ai · ORBIT // Cloudy_Day Security Suite

Cloud platforms

Degraded / minor incident Scaleway status

scaleway.com · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

Scaleway's status page shows “Degraded / minor incident” in Excellence and fr-par-1; the vendor is identified the cause. User reports haven't spiked, so wide impact isn't visible yet.

confidence: low Vendor: minor issue · users: normal · routing: normal.

Vendor status vs. reality: Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal)

Regions mentioned: Excellence, fr-par-1, Apple Silicon

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started30 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the change5 h 20 min

Evidence

  • Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
  • Vendor stage: identified the cause on “[Support] Delays in ticket processing”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low
  • AS12876 prefixes seen by 100% of RIPE RIS peers. evidence confidence: medium

What we don't know: what is happening inside Scaleway's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from providers it may run on (inferred). Routing data shows reachability, not whether the app works.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “identified the cause”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: normal. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).

Who depends on whom

We don't map other services that depend on Scaleway. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Scaleway, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; routing visibility returning to normal; and whether dependents start reporting issues.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Scaleway. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

[Support] Delays in ticket processing

minor identified · started

3 updates

  1. investigating

    En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude. Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais. Nous vous remercions pour votre patience et votre compréhension. Due to a high volume of requests, the processing of ongoing tickets may take longer than usual. Our teams are fully mobilized to restore normal service and handle requests as quickly as possible. Thank you for your patience and understanding.

  2. identified

    En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude. Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais. Nous vous remercions pour votre patience et votre compréhension. Due to a high volume of requests, the processing of ongoing tickets may take longer than usual. Our teams are fully mobilized to restore normal service and handle requests as quickly as possible. Thank you for your patience and understanding.

  3. identified

    En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude. Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais. Nous vous remercions pour votre patience et votre compréhension. Due to a high volume of requests, the processing of ongoing tickets may take longer than usual. Our teams are fully mobilized to restore normal service and handle requests as quickly as possible. Thank you for your patience and understanding.

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next