Company Logo

Is there an Jira outage?

Jira status: Systems Active

Last checked: 5 minutes ago

Get notified about any outages, downtime or incidents for Jira and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Jira outages and incidents

Outage and incident data over the last 30 days for Jira.

There have been 10 outages or incidents for Jira in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Jira

Outlogger tracks the status of these components for Xero:

Administration Active
Authentication and User Management Active
Automation for Jira Active
Create and edit Active
Marketplace Active
Mobile Active
Notifications Active
Purchasing & Licensing Active
Search Active
Signup Active
Viewing content Active
Component Status
Administration Active
Authentication and User Management Active
Automation for Jira Active
Create and edit Active
Marketplace Active
Mobile Active
Notifications Active
Purchasing & Licensing Active
Search Active
Signup Active
Viewing content Active

Latest Jira outages and incidents.

View the latest incidents for Jira and check for official updates:

Updates:

  • Time: Jan. 12, 2024, 8:59 p.m.
    Status: Resolved
    Update: Between 10th January 11:00 PM (UTC) and 12th January 18:30 (UTC) some instances were facing an issue with receiving comment_updated webhooks. The incident is resolved now. Sorry for the inconveniences.

Updates:

  • Time: Jan. 12, 2024, 8:59 p.m.
    Status: Resolved
    Update: Between 10th January 11:00 PM (UTC) and 12th January 18:30 (UTC) some instances were facing an issue with receiving comment_updated webhooks. The incident is resolved now. Sorry for the inconveniences.

Updates:

  • Time: Jan. 12, 2024, 5:13 p.m.
    Status: Resolved
    Update: We experienced degraded SCIM provisioning from external Identity Providers for Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Access. The issue has been resolved and the service is operating normally.
  • Time: Jan. 12, 2024, 5:13 p.m.
    Status: Resolved
    Update: We experienced degraded SCIM provisioning from external Identity Providers for Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Access. The issue has been resolved and the service is operating normally.
  • Time: Jan. 12, 2024, 6:55 a.m.
    Status: Monitoring
    Update: A fix for the bottleneck identified in the Group synchronization process for SCIM Provisioning has been made. We are seeing processing start to return to normal levels and will be monitoring over the next few hours. The team is all hands on deck to keep improving the situation.
  • Time: Jan. 12, 2024, 6:55 a.m.
    Status: Monitoring
    Update: A fix for the bottleneck identified in the Group synchronization process for SCIM Provisioning has been made. We are seeing processing start to return to normal levels and will be monitoring over the next few hours. The team is all hands on deck to keep improving the situation.
  • Time: Jan. 11, 2024, 10:36 p.m.
    Status: Monitoring
    Update: The bottleneck in the Group synchronization process for SCIM Provisioning has seen considerable improvement due to recent changes, but it is still under work. The team is all hands on deck to keep improving the situation.
  • Time: Jan. 11, 2024, 10:36 p.m.
    Status: Monitoring
    Update: The bottleneck in the Group synchronization process for SCIM Provisioning has seen considerable improvement due to recent changes, but it is still under work. The team is all hands on deck to keep improving the situation.
  • Time: Jan. 11, 2024, 6:54 p.m.
    Status: Monitoring
    Update: The bottleneck in the Group synchronization process for SCIM Provisioning is still under work. The team is all hands on deck to improve the situation.
  • Time: Jan. 11, 2024, 6:54 p.m.
    Status: Monitoring
    Update: The bottleneck in the Group synchronization process for SCIM Provisioning is still under work. The team is all hands on deck to improve the situation.
  • Time: Jan. 10, 2024, 7:56 p.m.
    Status: Monitoring
    Update: The bottleneck in the Group synchronization process for SCIM Provisioning is still under work. We are closely monitoring the service.
  • Time: Jan. 10, 2024, 7:56 p.m.
    Status: Monitoring
    Update: The bottleneck in the Group synchronization process for SCIM Provisioning is still under work. We are closely monitoring the service.
  • Time: Jan. 10, 2024, 3:17 a.m.
    Status: Monitoring
    Update: We have identified a bottleneck in the Group synchronisation process for SCIM Provisioning. We have increased the resources allocated to the process in order to mitigate the issue. We are now monitoring the service.
  • Time: Jan. 10, 2024, 3:17 a.m.
    Status: Monitoring
    Update: We have identified a bottleneck in the Group synchronisation process for SCIM Provisioning. We have increased the resources allocated to the process in order to mitigate the issue. We are now monitoring the service.
  • Time: Jan. 9, 2024, 10:03 p.m.
    Status: Investigating
    Update: We are investigating cases of degraded performance when SCIM provisioning users/groups for Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Access Cloud customers. We will provide more details shortly.
  • Time: Jan. 9, 2024, 10:03 p.m.
    Status: Investigating
    Update: We are investigating cases of degraded performance when SCIM provisioning users/groups for Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Access Cloud customers. We will provide more details shortly.

Updates:

  • Time: Dec. 28, 2023, 3:25 a.m.
    Status: Postmortem
    Update: ### **SUMMARY** On Dec 18, 2023, between 12:29 p.m. and 3:35 p.m. UTC, Dec 18, 2023, Atlassian's cloud customers using Atlas, Bitbucket Cloud, Compass, Confluence Cloud, Jira Service Management, Jira Software, Jira Work Management, Jira Product Discovery products were unable to search for users or use the "@mention" functionality. Customers' user search results failed or were delayed as Atlassian's service returning user search results was degraded in several regions. The incident originated from a computationally intensive operation that was triggered multiple times in rapid succession, resulting in degraded performance of Atlassian's user search service across several regions. Notably, customers in the EU west region were most affected. The incident was detected within 2 minutes by automated monitoring, and our team promptly took action by recovering unhealthy systems and scaling up the service's infrastructure temporarily. The resolution process concluded in 3 hours and 06 minutes. ### **IMPACT** The overall impact was between Dec 18, 2023, between 12:29 p.m. UTC and Dec 18, 2023, 3:35 p.m. UTC. The Incident caused service disruption to cloud customers worldwide. Customers experienced delayed or failed user searches when using the following Atlassian cloud products: * Atlas * Bitbucket Cloud * Compass * Confluence Cloud * Jira Service Management * Jira Software * Jira Work Management * Jira Product Discovery ### **ROOT CAUSE** The incident stemmed from Atlassian's user search service receiving commands to process multiple computationally intensive operations in rapid succession. These operations were directed at the same customer data set, and therefore overloaded resources within a clustered database system, leading to memory exhaustion and subsequent unresponsiveness to user search requests.  ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** To prevent a recurrence of such incidents, we are implementing the following measures: * Implement a mechanism to queue computationally intensive operations in order to avoid overloading the resources within the systems and process them without impact on customer experience. * Fine-tune our clustered database settings to mitigate the impact of resource exhaustion on the overall system.  We apologize to customers whose services were affected during this incident; we are taking immediate steps to improve the service’s resiliency. Thanks, Atlassian Customer Support
  • Time: Dec. 28, 2023, 3:25 a.m.
    Status: Postmortem
    Update: ### **SUMMARY** On Dec 18, 2023, between 12:29 p.m. and 3:35 p.m. UTC, Dec 18, 2023, Atlassian's cloud customers using Atlas, Bitbucket Cloud, Compass, Confluence Cloud, Jira Service Management, Jira Software, Jira Work Management, Jira Product Discovery products were unable to search for users or use the "@mention" functionality. Customers' user search results failed or were delayed as Atlassian's service returning user search results was degraded in several regions. The incident originated from a computationally intensive operation that was triggered multiple times in rapid succession, resulting in degraded performance of Atlassian's user search service across several regions. Notably, customers in the EU west region were most affected. The incident was detected within 2 minutes by automated monitoring, and our team promptly took action by recovering unhealthy systems and scaling up the service's infrastructure temporarily. The resolution process concluded in 3 hours and 06 minutes. ### **IMPACT** The overall impact was between Dec 18, 2023, between 12:29 p.m. UTC and Dec 18, 2023, 3:35 p.m. UTC. The Incident caused service disruption to cloud customers worldwide. Customers experienced delayed or failed user searches when using the following Atlassian cloud products: * Atlas * Bitbucket Cloud * Compass * Confluence Cloud * Jira Service Management * Jira Software * Jira Work Management * Jira Product Discovery ### **ROOT CAUSE** The incident stemmed from Atlassian's user search service receiving commands to process multiple computationally intensive operations in rapid succession. These operations were directed at the same customer data set, and therefore overloaded resources within a clustered database system, leading to memory exhaustion and subsequent unresponsiveness to user search requests.  ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** To prevent a recurrence of such incidents, we are implementing the following measures: * Implement a mechanism to queue computationally intensive operations in order to avoid overloading the resources within the systems and process them without impact on customer experience. * Fine-tune our clustered database settings to mitigate the impact of resource exhaustion on the overall system.  We apologize to customers whose services were affected during this incident; we are taking immediate steps to improve the service’s resiliency. Thanks, Atlassian Customer Support
  • Time: Dec. 19, 2023, 3:28 a.m.
    Status: Resolved
    Update: It has been resolved. Atlassian's cross product user search is working.
  • Time: Dec. 19, 2023, 3:28 a.m.
    Status: Resolved
    Update: It has been resolved. Atlassian's cross product user search is working.
  • Time: Dec. 18, 2023, 4:23 p.m.
    Status: Investigating
    Update: Atlassian's cross product user search service is currently healthy. Searches for users within Atlassian products are working as expected. We are in the process of investigating the root cause of this incident.
  • Time: Dec. 18, 2023, 4:23 p.m.
    Status: Investigating
    Update: Atlassian's cross product user search service is currently healthy. Searches for users within Atlassian products are working as expected. We are in the process of investigating the root cause of this incident.
  • Time: Dec. 18, 2023, 4:06 p.m.
    Status: Investigating
    Update: Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.
  • Time: Dec. 18, 2023, 4:06 p.m.
    Status: Investigating
    Update: Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.
  • Time: Dec. 18, 2023, 4:02 p.m.
    Status: Investigating
    Update: Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.
  • Time: Dec. 18, 2023, 4:02 p.m.
    Status: Investigating
    Update: Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.
  • Time: Dec. 18, 2023, 4:01 p.m.
    Status: Investigating
    Update: Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.
  • Time: Dec. 18, 2023, 4:01 p.m.
    Status: Investigating
    Update: Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.
  • Time: Dec. 18, 2023, 3:04 p.m.
    Status: Investigating
    Update: We are investigating reports of intermittent errors for <SOME/ALL> Atlassian, Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Align, Jira Product Discovery, Atlas, and Compass Cloud customers. We will provide more details once we identify the root cause.
  • Time: Dec. 18, 2023, 3:04 p.m.
    Status: Investigating
    Update: We are investigating reports of intermittent errors for <SOME/ALL> Atlassian, Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Align, Jira Product Discovery, Atlas, and Compass Cloud customers. We will provide more details once we identify the root cause.

Updates:

  • Time: Dec. 13, 2023, 4:34 p.m.
    Status: Resolved
    Update: 13-Dec-2023 12.30 PM UTC: Most customers have confirmed that they are no longer facing the issue, we will continue to monitor.
  • Time: Dec. 13, 2023, 4:26 p.m.
    Status: Identified
    Update: 13-Dec-2023 12:00 PM UTC: The incident root cause is currently being investigated and the most likely cause is related to the Jira SSR(Server Side Rendering) Frontend gateway service not being accessible and falling back to an HTML blank page. It is a rare use case that will be mitigated in the next hours by properly handling the falling back logic.
  • Time: Dec. 13, 2023, 4:25 p.m.
    Status: Investigating
    Update: 13-Dec-2023 7.30 AM UTC: Some customers started reporting that they are no longer facing the issue.
  • Time: Dec. 13, 2023, 4:24 p.m.
    Status: Investigating
    Update: 13-Dec-2023 6.40 AM UTC: We are investigating cases were Jira Software, JSM appears to not be loading correctly for some users in Asia Pacific and Europe region. Customers were greeted with a white screen and black lines.

Check the status of similar companies and alternatives to Jira

Atlassian
Atlassian

Systems Active

Zoom
Zoom

Issues Detected

Dropbox
Dropbox

Systems Active

Miro
Miro

Systems Active

TeamViewer
TeamViewer

Systems Active

Lucid Software
Lucid Software

Systems Active

Restaurant365
Restaurant365

Systems Active

Mural
Mural

Systems Active

Zenefits
Zenefits

Systems Active

Retool
Retool

Systems Active

Splashtop
Splashtop

Systems Active

Hiver
Hiver

Systems Active

Frequently Asked Questions - Jira

Is there a Jira outage?
The current status of Jira is: Systems Active
Where can I find the official status page of Jira?
The official status page for Jira is here
How can I get notified if Jira is down or experiencing an outage?
To get notified of any status changes to Jira, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Jira every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Jira do?
Jira is a project management tool that helps agile teams plan, track, and release software. It enables users to achieve seemingly impossible tasks.

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free