Jira Software favicon

Jira Software outage on 2026-11-02

atlassian.com
November 2026 2 Major incident

Jira Software had a 32 minute outage starting at 00:10 UTC on 2 November 2026, with fields missing across Work Items for some users. Atlassian traced it to a configuration change on their side, reverted it, and confirmed a fix by 00:38 UTC.

Started

00:10 UTC

Duration

Lasted 32m

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: Automation for Jira, Viewing content, Search

What happened?

Atlassian's status page reports one incident on this day, starting at 00:10 UTC and lasting 32 minutes. The problem was fields missing across Jira Work Items for some users, with knock-on effects on Viewing content, Search, and Automation for Jira. At 00:10 UTC Atlassian said it was aware of an issue impacting fields across Work Items in Jira family products, including impacts to searching and automations on those fields, and that it was investigating with urgency. By 00:25 UTC it had identified a configuration change as the likely cause, reverted it, and reported early signs of recovery. At 00:38 UTC it marked the incident resolved, stating that field related operations across Jira, Jira Software Management, Jira Work Management and Jira Product Discovery should now be fully operational. That is three updates in total, all shown here, and the cause given is Atlassian's own, not an outside guess. No user reports were filed during this window on the record available. Over the past 90 days Jira Software has logged 15 incidents with a median duration of 2 hours 2 minutes, so this one resolved faster than typical. Across all time Atlassian has recorded 468 incidents for this product, averaging 6 per month. No separate post-mortem beyond these three updates has been published.

Learning

UptimeRobot's own checks over the past 30 days show 2 incidents for this product, both resolved, with a median duration of 59 minutes, a different shape from what Atlassian reported for this specific event. That difference is not a contradiction. External uptime checks typically probe whether a service responds at all, while this incident was about specific fields failing to load inside Work Items, a fault that can sit entirely within Atlassian's application logic and never trip a simple availability check. A product can answer every ping correctly while a feature inside it, like field rendering or search indexing, is broken for real users. This is the shape to watch for in your own product too: the parts that fail quietly, inside a working response, rather than taking the whole thing down. 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.