outages.live
Live
ScalewayIncident ·

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

DegradedOfficial update
0

Scaleway Transactional Email has degraded email delivery to Microsoft consumer domains such as Outlook and Hotmail. All sending pools are affected. Scaleway reports the state as identified. Delivery can take up to 1 hour. The cause is external, and Scaleway monitors MX timeouts.

State

Identified

Started

Ongoing for

47 min

Worst impact

Degraded

Timeline

2 updates
20:0720:1920:3020:4220:54
DegradedUpdate postedTimes in UTC

Identified

47 min 100%

Updates

Times in UTC

As posted by Scaleway

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

Identified

- Start: 2026-11-12 ~18:45 UTC (19:45 CET) - Impact: Email delivery to Microsoft consumer domains significantly delayed. Backlog of ~2,500 emails pending (incl. short-TTL OTP/auth messages at risk of expiry drops). All sending pools affected; partial delivery continues (8/min vs 25–30/min nominal). - Symptoms / findings: TCP connection timeouts (SYN unanswered) to Microsoft MX endpoints (52.101.x.x), spread across 10+ sending IPs and all pools. No connection refusals, no SMTP-level throttling — behavior consistent with a Microsoft-side infrastructure degradation, not reputation filtering. Deferrals peaked at ~1,000 MX-unavailable events / 10 min. No other destination domains affected beyond Microsoft consumer properties (+ unrelated, pre-existing Proximus/gtm-tc2 slowness tracked separately). - External cause: Microsoft 365 / Exchange Online outage, tracked by Microsoft as EX1550543 — acknowledged ~19:37 UTC, fix deployed ~18:30 CET, gradual recovery in progress. Refs: @MSFT365Status,

Affected components

2
Transactional EmailElements - Products - Transactional Email

Scaleway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

76

Days with an incident

38

Median duration

7 h 41 min

This incident

90% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

22 days
median 7 h 41 min
90 days agoToday

Other Scaleway incidents

All incidents

Scaleway·[Network] [DC3]- Room S45 rack D14 - Public switch reboot

Scaleway reports a public switch problem in room S45, rack D14 at DC3. This affects Dedibox services in that datacenter. Scaleway identified the problem. Scaleway will replace the affected network switch on Friday, November 13, 2026, starting at 10:00 a.m. CET.

Degraded

Scaleway·[Network] [DC3]- Room S45 rack D14 - Public switch reboot

At 2026-11-12 16:53:02 CET, the public switch in DC3 room S45 rack D14 rebooted. All servers attached to it have lost public connectivity for approximately 10 mins.

Resolved

Scaleway·[Containers/Functions] - [fr-par] - private endpoints might not be available

Scaleway reports that private endpoints were not available for a subset of Serverless Containers and Serverless Functions in the fr-par region. This affected fr-par-1, fr-par-2 and fr-par-3. The incident is resolved and lasted about 1 hour and 30 minutes.

Resolved

Scaleway·[Generative-Apis] [fr-par] - mistral-small-3.2-24b-instruct-2506 outage

[11/12 - 9:45 UTC+1] The incident has been mitigated, service is back to normal

Resolved

Scaleway·[ElasticMetal] - [world] - The private_network option is not working as expected in the Terraform provider.

The privatenetwork option does not work as expected in the Scaleway Terraform provider for Elastic Metal in all regions. Scaleway reports that it is investigating the problem.

Degraded

Follow Scaleway

Your coding agent knows when Scaleway is down, and tells you when a failure is theirs, not yours. You can also get Scaleway incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "scaleway" and tell me if Scaleway has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=scaleway
Slack
/feed subscribe https://outages.live/feed.xml?providers=scaleway

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane