Live

Email Delivery delays to Microsoft inboxes

0

Email delivery delays affect messages sent through Braze to Microsoft inboxes. This includes outlook.com, hotmail.com, live.com, and Microsoft 365 business domains. Braze reports the status as identified. Braze services continue to operate fully. Affected messages continue to be retried.

State

Identified

Started

Ongoing for

55 min

Worst impact

Notice

Timeline

3 updates
11:5612:1012:2412:3712:51
NoticeUpdate postedTimes in UTC

Identified

52 min 95%

Resolved

3 min 5%

Updates

Times in UTC

As posted by Braze

Identified

Microsoft is currently experiencing a global outage affecting the email services it provides to its customers. This is impacting the delivery of emails sent through Braze to recipients whose mailboxes are hosted by Microsoft, including outlook.com, hotmail.com, live.com addresses, as well as business domains that use Microsoft 365. Delivery to these recipients is delayed and, as of today, 13 November 2026, affected messages continue to be retried. Braze services continue to fully operational at this time.

Resolved
Identified

Microsoft is currently experiencing a global outage affecting the email services it provides to its customers. This is impacting the delivery of emails sent through Braze to recipients whose mailboxes are hosted by Microsoft, including outlook.com, hotmail.com, live.com addresses, as well as business domains that use Microsoft 365. Delivery to these recipients is delayed and, as of today, 13 November 2026, affected messages continue to be retried. Braze services continue to fully operational at this time.

Affected components

2
EmailGlobal Messaging Channels - Email

Braze in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

3

Median duration

2 h 25 min

This incident

62% shorter than the median

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

6 h 52 min
median 2 h 25 min
90 days agoToday

Other Braze incidents

All incidents

Follow Braze

Your coding agent knows when Braze is down, and tells you when a failure is theirs, not yours. You can also get Braze 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 "braze" and tell me if Braze 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=braze
Slack
/feed subscribe https://outages.live/feed.xml?providers=braze

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane