> Markdown version of https://getuptimely.com/service-status/jira — the page itself is the canonical copy. Service status # Jira status Is Jira down? This is Jira’s current status, its components and its recent incidents, read from [Jira’s official status page](https://jira-software.status.atlassian.com) and refreshed every 2 minutes. ## All Systems Operational As reported by Jira’s status page, read Oct 24, 2026, 18:09 UTC. ## Components __Jira components and their status__ | Component | Status | | ---------------------------------- | ----------- | | Viewing content | Operational | | Create and edit | Operational | | Authentication and User Management | Operational | | Search | Operational | | Notifications | Operational | | Administration | Operational | | Marketplace | Operational | | Mobile | Operational | | Purchasing & Licensing | Operational | | Signup | Operational | | Automation for Jira | Operational | | Webhooks | Operational | What a [degraded performance](https://getuptimely.com/glossary/degraded-performance) status means, and how much downtime an SLA allows: [the uptime calculator](https://getuptimely.com/tools/uptime-calculator). ## Recent Jira incidents - **[Jira - Project Sidebar Loading Degradation](https://stspg.io/czwk831b76lg)** · Oct 21, 2026, 14:28 UTC · resolved, minor impact, lasted 1 h 16 min On October 21, 2026, JIRA, JSM, JPD, and JWM users may have experienced performance degradation impacting the project sidebar and navigation. The issue has now been resolved, and the service is operating normally for all affected customers. - **[Job processing and scheduling is degraded affecting multiple Atlassian products](https://stspg.io/037ndsk7y1d4)** · Oct 1, 2026, 02:55 UTC · postmortem, major impact, lasted 4 h 56 min \### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed… - **[Degraded Performance Viewing Issues and Boards](https://stspg.io/d356gxdfnsjm)** · Sep 24, 2026, 13:54 UTC · resolved, minor impact, lasted 1 h 59 min On September 24th 2026, some Jira and JSM users in the US region may have experienced a performance degradation impacting Jira issue creation, issue viewing, and board loading. The issue has now been resolved, and the service is operating normally for all affected customers. - **[Degraded Performance Accessing Jira](https://stspg.io/cvmh1bk43hff)** · Sep 24, 2026, 08:52 UTC · resolved, lasted 2 h 54 min On Sept 24th, 2026, between 07:28 to 08:08 UTC, some Jira users may have experienced errors or degraded performance when accessing Jira and viewing issues. The issue has now been resolved and the service is operating normally for all customers. - **[Degraded performance affecting Jira Software and Jira Service Management](https://stspg.io/z2x6g434dy91)** · Sep 11, 2026, 07:46 UTC · postmortem, minor impact, lasted 51 min \### Summary On September 11, 2026, between 07:02 and 07:56 UTC, Atlassian customers primarily from the EU region and some from APAC region using Jira and Jira Service Management products were unable to view work items or access boards consistently. The event was triggered by a… - **[Disrupted JIRA availability in US East](https://stspg.io/tq5053jz6616)** · Sep 3, 2026, 15:57 UTC · postmortem, critical impact, lasted 1 h 5 min \### Summary On September 3, 2026, between 14:52 and 17:02 UTC, Atlassian customers using Jira and Jira Service Management in the US-East region experienced intermittent errors and degraded access to core Jira experiences, including Rovo, viewing issues, boards, navigation,… - **[Degraded performance of JIRA](https://stspg.io/j81jwhmpzlrx)** · Sep 1, 2026, 17:09 UTC · resolved, minor impact, lasted 4 h 26 min On September 1, some JIRA users may have experienced performance degradation affecting forms functionality. The issue has now been resolved, and the service is operating normally for all affected customers. - **[Jira - Work Item transition failures](https://stspg.io/rggy5gzxqj68)** · Sep 1, 2026, 09:12 UTC · resolved, minor impact, lasted 2 h 31 min On 1st Sept 2026, between 04:22 UTC to 10:59 UTC, some Jira users may have experienced service disruptions. The issue has now been resolved and the service is operating normally for all the customers. - **[Fetching mails from Microsoft accounts producing errors and preventing email based creation of Jira work items](https://stspg.io/0zc4g3y79r4b)** · Aug 31, 2026, 18:28 UTC · resolved, major impact, lasted 10 h 50 min We're now seeing full recovery across Atlassian services that have been impacted, and this incident is now resolved. For those continuing to experience issues relating to this incident we encourage you to please check https://status.cloud.microsoft/ as they continue to provide… - **[Issues accessing multiple Atlassian products in some regions](https://stspg.io/y1ckp74gvrvz)** · Aug 27, 2026, 04:22 UTC · postmortem, critical impact, lasted 54 min \*\*SUMMARY\*\* On August 27, 2026, between 03:51 and 04:35 UTC, Atlassian customers in the Western Europe and Southeast APAC regions were unable to reach Atlassian Cloud products, including Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo… - **[Notifications are delayed](https://stspg.io/dx83596c0c40)** · Aug 25, 2026, 08:42 UTC · resolved, major impact, lasted 5 h 51 min On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers. - **[Degraded performance of Notifications](https://stspg.io/m143x9xkkh7n)** · Aug 24, 2026, 19:22 UTC · resolved, minor impact, lasted 3 h 53 min On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally. There… - **[Performance and access related issues with Jira](https://stspg.io/n736m77txn89)** · Aug 7, 2026, 11:30 UTC · resolved, critical impact, lasted 1 h 21 min On August 7th - 2026, between 10:27 UTC to 11:49 UTC, some users in the Central European region may have experienced service access issues. The issue has now been resolved and the service is operating normally for all the customers. - **[Degraded performance of JIRA](https://stspg.io/d7xrb3fk7f4x)** · Aug 7, 2026, 01:24 UTC · resolved, minor impact, lasted 22 min On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers. - **[Degraded performance of Jira Automation rules](https://stspg.io/0klgd4y08tf5)** · Jul 20, 2026, 20:18 UTC · resolved, minor impact, lasted 28 h 38 min Our team has been able to validate that all rule executions are performing normally and this issue is now resolved. Source: [Jira](https://jira-software.status.atlassian.com), Jira’s public status page, read Oct 24, 2026, 18:09 UTC. Uptimely is not affiliated with Jira; incident text is Jira’s own. ## Is it down for you, or for everyone? A status page shows what the vendor has confirmed, which often lags what users see. Your own network, account or region can also be the cause. ## Get alerted when Jira has an incident Uptimely’s External Status Page monitor watches Jira’s status page and alerts your team by email, SMS, phone call, Slack, Discord or browser push when it reports a problem, next to the monitors for your own services. [Watch Jira free →](https://app.getuptimely.com/accounts/register) ## Status of similar services - [Notion status](https://getuptimely.com/service-status/notion) - [Figma status](https://getuptimely.com/service-status/figma) - [Canva status](https://getuptimely.com/service-status/canva) - [Linear status](https://getuptimely.com/service-status/linear) - [Asana status](https://getuptimely.com/service-status/asana) - [Trello status](https://getuptimely.com/service-status/trello) - [Confluence status](https://getuptimely.com/service-status/confluence) - [Miro status](https://getuptimely.com/service-status/miro) - [Dropbox status](https://getuptimely.com/service-status/dropbox) - [Box status](https://getuptimely.com/service-status/box) [Every service status we track](https://getuptimely.com/service-status) ### Is Jira down right now? The status at the top of this page is Jira's own, read from its public status page every couple of minutes. It shows what Jira's team has confirmed. ### Where is Jira's official status page? Jira publishes its status at https://jira-software.status.atlassian.com. This page shows the same data with the recent incident history in one place, and links each incident to Jira's own write-up. ### Why does Jira not work for me when its status says operational? A status page lists the incidents a vendor has confirmed, and confirmation takes time: problems often reach users minutes before they reach the status page, and some partial or regional problems never appear on it. Your own network, account or region can also be the cause. ### How can I get alerted when Jira has an incident? Add an External Status Page monitor in Uptimely pointed at https://jira-software.status.atlassian.com. It reads the page on a schedule and alerts your team by email, SMS, phone call, Slack, Discord or browser push when Jira reports a problem, beside the monitors for your own services.