Jira Software favicon

Jira Software outage on 2026-11-13

atlassian.com
November 2026 13 Minor incident

If you rely on Jira or Jira Service Management picking up emails from Microsoft-connected mailboxes, you lost that for roughly a full day. Atlassian says the fault sat with Microsoft 365, not with Jira itself, and the incident ran 24 hours 8 minutes before it was marked resolved.

Started

06:01 UTC

Duration

Lasted 1d 0h

Source

IsDown

Next time

Jira Software is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: Create and edit

What happened?

Atlassian's status page opened this incident at 06:01 UTC, reporting elevated failures processing incoming mail in Jira and JSM, with a reduction in the number of emails handled. The one component listed as affected is Create and edit, which covers the part of Jira that turns an inbound email into a new issue or a comment on an existing one. From the first update, Atlassian pointed at Microsoft, linking to Microsoft 365's own status page and describing this as a knock-on effect of a Microsoft service degradation rather than a Jira-side fault. The 07:32 update repeated that framing almost word for word: failures continuing, teams monitoring Microsoft's recovery, nothing new to add. At 12:34 the status moved to identified, with Atlassian noting signs of improvement but some failures still occurring. By 16:17, under a monitoring label, Atlassian reported lower failure rates and said it would post again only if something changed significantly. The incident was then resolved at 06:07 UTC the next day, with Atlassian stating that incoming email processing for Microsoft-connected mailboxes had returned to normal. Across the whole window Atlassian published five updates and attributed all of it to Microsoft, never describing an internal fix on its own side. No user reports were filed during this window. Atlassian's 90 day history shows 14 incidents with a median duration of 2 hours 45 minutes, so this one ran far longer than typical for this component.

Learning

This incident was a mail ingestion failure sitting between two vendors, Microsoft on the sending side and Atlassian on the receiving side, and neither Jira's own uptime nor a simple ping to Jira's web app would have shown it. Jira's core interface, boards and tickets kept working the whole time. The thing that broke was a background pipe, incoming email being parsed into issues, which only shows up if you are actually watching that specific flow or waiting on an email-created ticket that never arrives. Our own 30 day figures for this service show 3 incidents, all resolved, with a median duration of 1h 27m, a different shape entirely from this one, which is a reminder that a status page's own history and a single long incident tied to a third party can both be true at once. If your workflow depends on email-to-issue creation, a clean check of Jira's front end tells you nothing about whether that pipe is open. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.