outages.live
Live

Jira

Jira is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

15

Days with an incident

12

Median duration

1 h 59 min

Longest incident

10 h 50 min

Components

12
Viewing content Operational
90 days ago11 days with an incidentToday
Create and edit Operational
90 days ago8 days with an incidentToday
Authentication and User Management Operational
90 days ago7 days with an incidentToday
Search Operational
90 days ago8 days with an incidentToday
Notifications Operational
90 days ago8 days with an incidentToday
Administration Operational
90 days ago7 days with an incidentToday
Marketplace Operational
90 days ago7 days with an incidentToday
Mobile Operational
90 days ago7 days with an incidentToday
Purchasing & Licensing Operational
90 days ago7 days with an incidentToday
Signup Operational
90 days ago7 days with an incidentToday
Automation for Jira Operational
90 days ago9 days with an incidentToday
Webhooks Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Nov 2, 2026

Duration28 min00:10 to 00:38Fields missing across Jira Work Items for some usersPartial outage

Jira Work Items fields did not work for some users. This incident affected Viewing content, Search, and Automation for Jira. Jira reports that the issue is resolved. The outage lasted 28 minutes.

Oct 21, 2026

Duration1 h 16 min14:28 to 15:45Jira - Project Sidebar Loading DegradationDegraded

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.

Oct 1, 2026

Duration4 h 56 min02:55 to 07:51Job processing and scheduling is degraded affecting multiple Atlassian productsPartial outage

### 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 background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recu

Sep 24, 2026

Duration1 h 59 min13:54 to 15:53Degraded Performance Viewing Issues and BoardsDegraded

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.

Duration2 h 54 min08:52 to 11:46Degraded Performance Accessing JiraNotice

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.

Sep 11, 2026

Duration51 min07:46 to 08:37Degraded performance affecting Jira Software and Jira Service ManagementDegraded

### 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 backward-incompatible internal configuration rollout in the underlying graph data platform. The incident was detected within 3 minutes by our automated monitoring system and mitigated by rolling forward the stable deployment to all regions. The total time to resolution was about 54 minutes. ### IMPACT The overall impact occurred between September 11, 2026, 07:02 UTC and September 11, 2026, 07:56 UTC on two products. During this period, some customers in the EU region using Jira and Jira Service Management experienced intermittent failures or degraded performance. We noted that a configuration failure prevented critical dependency services from scaling, which resulted in an outage for affected users. Jira and Jira

Sep 3, 2026

Duration1 h 5 min15:57 to 17:02Disrupted JIRA availability in US EastMajor outage

### 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, search-backed experiences, workflow-related actions. The event was triggered by a progressive rollout of a caching change in Atlassian's authorization service. The change increased cache traffic and caused saturation in the cache layer used for authorization checks, which then resulted in timeouts and service errors for some customers in the region. The incident was detected by our monitoring within approximately 12 minutes. We mitigated by deploying the affected cache service and disabling the feature flags associated with the new cache path. The total time to resolution was 2 hours and 10 minutes. ### IMPACT The overall impact occurred on September 3, 2026 between 14:52 and 17:02 UTC. During this period, some custo

Sep 1, 2026

Duration4 h 26 min17:09 to 21:35Degraded performance of JIRADegraded

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.

Duration2 h 31 min09:12 to 11:44Jira - Work Item transition failuresDegraded

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.

Aug 31, 2026

Duration10 h 50 min18:28 to 05:18Fetching mails from Microsoft accounts producing errors and preventing email based creation of Jira work itemsPartial outage

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 further updates about additional services.

Aug 27, 2026

Duration54 min04:22 to 05:16Issues accessing multiple Atlassian products in some regionsMajor outage

**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 Search, and Talent. The event was triggered by a defective code change to the routing layer of one of our proxy fleets. This led to HTTP 404 errors being served to all customer traffic through these proxy fleets in Western Europe and Southeast APAC regions. The incident was detected within 1 minute by our automated monitoring systems, and mitigated by rolling back to the previous configuration release, which put the proxy fleet into a known good state. After the proxy fleet recovered, some Jira and Confluence customers (regardless of location) received HTTP 503 errors between 04:33 and 04:53 UTC as server fleets adjusted to the influx of traffic. **IMPACT** The overall impact was split into two discrete periods: - Fi

Aug 25, 2026

Duration5 h 51 min08:42 to 14:33Notifications are delayedPartial outage

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.

Aug 24, 2026

Duration3 h 53 min19:22 to 23:15Degraded performance of NotificationsDegraded

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 may be older notifications that are being processed, and we expect them to be completed in next few hours.

Aug 7, 2026

Duration1 h 21 min11:30 to 12:52Performance and access related issues with JiraMajor outage

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.

Duration22 min01:24 to 01:46Degraded performance of JIRADegraded

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.

Follow Jira

Your coding agent knows when Jira is down, and tells you when a failure is theirs, not yours. You can also get Jira incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "jira" and tell me if Jira has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=jira
Slack
/feed subscribe https://outages.live/feed.xml?providers=jira

Go from tracking outages to fixing production issues with Polylane.

Try Polylane