Skip to main content
Menu
Chargebee

Incident

Microsoft 365 Service Degradation

Degraded Lasted 1d 5h · started · Chargebee's page

DWN-0941bed3d6

Level
confirmed
Worst impact
Degraded
Components
Microsoft 365
Down Index
34of 100

Summary

Chargebee says that, due to an ongoing Microsoft 365 service outage, merchants using custom SMTP with Microsoft 365 may see delayed or failed email notifications. The provider is monitoring and says it will automatically retry pending notifications once the service is restored.

Written by anthropic/claude-haiku-5.5 from Chargebee's own updates.

What to do

  • Check whether you use Chargebee Microsoft 365. Check your stack

    Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1d 5h it lasted.

    Anything that failed between 2026-11-13 07:32 UTC and 2026-11-14 12:47 UTC may need a replay.
  • Subscribe to Chargebee's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=chargebee works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Chargebee 2

  1. monitoring

    Due to an ongoing Microsoft 365 service outage, merchants using custom SMTP with Microsoft 365 may experience delayed or failed email notifications. We are monitoring the situation and will automatically retry any pending notifications once the service is restored. More info: https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect

    provider

  2. resolved

    Microsoft has fully restored their 365 services. Custom SMTP email notifications are fully restored. We apologize for any disruption this caused.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-0941bed3d6

Is Chargebee still down?

No, this incident was resolved 2026-11-14 12:47 UTC. For Chargebee's live state, see https://down.guide/providers/chargebee.

How long did it last?

1d 5h, from 2026-11-13 07:32 UTC to 2026-11-14 12:47 UTC, by the times Chargebee posted.

What was affected?

Chargebee named Microsoft 365.

What caused it?

Chargebee hasn't published a root cause. If it does, it shows here.

Where does this come from?

Chargebee's official status page, https://status.chargebee.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.