Jira Software favicon

Jira Software outage on 2026-10-21

atlassian.com
October 2026 21 Minor incident

Jira Cloud's project sidebar and navigation broke down for 1h 27m on 21 October 2026. The fault sat on Atlassian's side, affecting viewing content across Jira, JSM, JPD and JWM.

Started

14:28 UTC

Duration

Lasted 1h 27m

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: Viewing content

What happened?

Atlassian logged one incident on 21 October 2026, starting at 14:28 UTC and running for 1h 27m. The title was "Jira - Project Sidebar Loading Degradation", and the affected component was viewing content, specifically the project sidebar and navigation inside Jira Cloud. The first update said users may have encountered timeouts or missing menus when trying to access project views, and that teams were analysing telemetry to find a mitigation. At 15:01 UTC Atlassian reported mitigations in place and recovery across navigation services, with sidebars loading as expected again, though they kept monitoring before confirming resolution. The final update at 15:45 UTC closed the incident, stating that JIRA, JSM, JPD and JWM users may have experienced performance degradation impacting the sidebar and navigation, and that service was operating normally for all affected customers. Atlassian did not publish any explanation of what caused the degradation, in this incident or any follow-up. No user reports were filed during the window on this page's record. The whole incident ran through three updates: investigating, monitoring, resolved. That is the entire public record for this day, there is nothing else to characterise beyond this one incident.

Learning

This incident failed at the application layer inside Jira Cloud's own navigation service, not at the network or infrastructure level, which is why checking your own endpoints or API calls against Jira would not necessarily have caught it. A sidebar or menu that times out or goes missing while the rest of a page responds normally is a layer problem, not a connectivity one, and that distinction matters when you are trying to work out whether an issue is yours or theirs. Over the past 90 days Atlassian has logged 14 incidents with a median duration of 2 hours 18 minutes, so a 1h 27m outage sits on the shorter side of what is normal for this service. UptimeRobot's own 30 day checks recorded 4 incidents, all resolved, with a median duration of 2h 29m, a pattern consistent with Atlassian's own figures even though the specific symptom here, a broken sidebar, is the kind of partial degradation that an external uptime check can miss while real users are still stuck staring at missing menus. 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.