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 Transactional Email and fr-par-1; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet.

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

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: Transactional Email, 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 51 min

Evidence

  • Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
  • Vendor stage: resolved on “[Transactional Email] - world - Delayed email delivery to Microsoft domains (Outlook/Hotmail)”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low

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 routing / bgp, 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 “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data. 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; 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

[Transactional Email] - world - Delayed email delivery to Microsoft domains (Outlook/Hotmail)

minor resolved · started · resolved

5 updates

  1. identified

    Start: 2026-11-12 ~18:45 UTC (19:45 CET) Impact: Some emails can take up 1 hour to be delivered. Cause: External. Microsoft 365 / Exchange Online outage Mitigation: Continuous monitoring of MX timeouts

  2. identified

    The Microsoft incident is still ongoing, with no estimated recovery time available. The growing backlog of emails to Microsoft is putting pressure on our delivery queue and could delay emails sent to other providers. To protect delivery performance for all other providers, we will cancel some pending emails addressed to Microsoft. If the incident exceeds our retry window, some remaining emails may also bounce. A bounce event will be generated for each affected email. Cancelled or bounced emails can be resent once Microsoft services are restored.

  3. identified

    In order to protect the current delivery to other email providers, and in addition with the previous action, we decided to refuse emails in destination to Microsoft's servers. The emails will be rejected with a "550 5.7.1 The recipient domain <domain> is temporarily not supported" SMTP message. The same behavior is expected on API side.

  4. monitoring

    We have reopened email delivery to Microsoft. The signals are positive so far, and our team is continuing to monitor the situation

  5. resolved

    This incident has been resolved.

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