Jira Software Outage History

Jira Software is up right now

Jira Software had 61 outages in the last 2 years totaling 300h 54m of downtime — averaging 2.5 incidents per month.

There were 61 Jira Software outages since June 24, 2025 totaling 300h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://jira-software.status.atlassian.com

Minor June 10, 2026

Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps

Detected by Pingoru
Jun 10, 2026, 04:55 AM UTC
Resolved
Jun 10, 2026, 06:31 AM UTC
Duration
1h 35m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
  1. investigating Jun 10, 2026, 04:55 AM UTC

    We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

  2. identified Jun 10, 2026, 05:39 AM UTC

    Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

  3. monitoring Jun 10, 2026, 06:14 AM UTC

    Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

  4. resolved Jun 10, 2026, 06:31 AM UTC

    We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Minor June 8, 2026

Users experiencing issues loading work items in Jira and JSM

Detected by Pingoru
Jun 08, 2026, 01:53 AM UTC
Resolved
Jun 08, 2026, 02:56 AM UTC
Duration
1h 2m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministration
Timeline · 3 updates
  1. investigating Jun 08, 2026, 01:53 AM UTC

    We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.

  2. identified Jun 08, 2026, 02:36 AM UTC

    We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

  3. resolved Jun 08, 2026, 02:56 AM UTC

    On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.

Read the full incident report →

Major June 6, 2026

Users experiencing issues loading work items in Atlassian products

Detected by Pingoru
Jun 06, 2026, 11:21 PM UTC
Resolved
Jun 07, 2026, 12:13 AM UTC
Duration
51m
Affected: Viewing contentCreate and edit
Timeline · 3 updates
  1. investigating Jun 06, 2026, 11:21 PM UTC

    We are aware of users currently experiencing loading work items across Atlassian products in some regions. We are investigating with urgency and will provide update within one hour.

  2. monitoring Jun 07, 2026, 12:07 AM UTC

    A fix has been implemented for the issues some customers have been experiencing with creating and viewing work items in Jira. We are now monitoring for this recovery and will update shortly with further confirmation.

  3. resolved Jun 07, 2026, 12:13 AM UTC

    The issues relating to viewing and creating work items in Jira should now be fully resolved.

Read the full incident report →

Minor June 2, 2026

Degraded performance of Jira and JSM automations in US East

Detected by Pingoru
Jun 02, 2026, 03:32 PM UTC
Resolved
Jun 02, 2026, 04:51 PM UTC
Duration
1h 18m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 2 updates
  1. investigating Jun 02, 2026, 03:32 PM UTC

    We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. Some customers may experiences delays in rule execution. We'll provide an update here within the next hour, or sooner if new information becomes available.

  2. resolved Jun 02, 2026, 04:51 PM UTC

    On June 6, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Previously delayed automation rules are expected to be completed within 12 hours.

Read the full incident report →

Minor May 20, 2026

Forge custom fields are not getting created

Detected by Pingoru
May 20, 2026, 09:17 AM UTC
Resolved
May 20, 2026, 02:14 PM UTC
Duration
4h 57m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
  1. investigating May 20, 2026, 09:17 AM UTC

    Users are reporting an issue with Forge custom fields not getting created on Jira work items page, after deploying an application. Our teams are investigating the issue and more updates will be shared within next 2 hour or sooner.

  2. investigating May 20, 2026, 11:20 AM UTC

    Our teams are actively working on the identifying the root cause and we will provide an update within 3 hours, or sooner if there is any significant progress. Thank you for your patience.

  3. identified May 20, 2026, 12:06 PM UTC

    Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 3 hours, or sooner if we have any meaningful developments to report. The impact is limited to new deployments with Forge custom fields on Jira work items, however existing deployments with custom fields are running without any issues.

  4. resolved May 20, 2026, 02:14 PM UTC

    The root cause has been identified and a fix has been applied. Full service restoration has been completed.

Read the full incident report →

Major May 6, 2026

Jira users unable to log time while on business board

Detected by Pingoru
May 06, 2026, 03:18 AM UTC
Resolved
May 06, 2026, 06:39 AM UTC
Duration
3h 21m
Affected: Create and edit
Timeline · 3 updates
  1. investigating May 06, 2026, 03:18 AM UTC

    We are investigating reports of users unable to log time while on business board. Our engineering teams are actively investigating and working to resolve the issue. We will provide more updates in next 1 hour.

  2. identified May 06, 2026, 04:16 AM UTC

    Our engineering teams have identified the cause and are in process of deploying a fix. We will share further updates in next 3 hours, or sooner if we have any meaningful developments to report.

  3. resolved May 06, 2026, 06:39 AM UTC

    The issue causing Jira users inability to log time on business board has been resolved. A fix was deployed to address the problem and the service is operating normally for all affected customers.

Read the full incident report →

Minor April 30, 2026

Delays in Jira webhook delivery

Detected by Pingoru
Apr 30, 2026, 08:59 AM UTC
Resolved
Apr 30, 2026, 02:56 PM UTC
Duration
5h 57m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
  1. investigating Apr 30, 2026, 08:59 AM UTC

    We are investigating reports of delays in webhook delivery. Customers may experience intermittent delays when receiving webhooks. Our engineering teams are actively investigating and working to resolve the issue. We will provide updates as more information becomes available.

  2. identified Apr 30, 2026, 10:05 AM UTC

    We have identified the cause of the delayed Jira webhook delivery and are deploying a fix. We will continue to provide updates as more information becomes available.

  3. monitoring Apr 30, 2026, 01:36 PM UTC

    A fix has been deployed to address the intermittent delays in Jira webhook delivery. We are actively monitoring the situation to confirm full recovery. We will continue to provide updates as available.

  4. resolved Apr 30, 2026, 02:56 PM UTC

    The issue causing intermittent delays in our webhook delivery has been resolved. A fix was deployed to address a resource constraint in our systems. Our monitoring shows webhook delivery is now operating normally.

Read the full incident report →

Critical April 14, 2026

Disrupted Rovo availability for Automation rules

Detected by Pingoru
Apr 14, 2026, 12:12 PM UTC
Resolved
Apr 14, 2026, 04:11 PM UTC
Duration
3h 58m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 5 updates
  1. investigating Apr 14, 2026, 12:12 PM UTC

    We are actively investigating reports of a partial service disruption affecting Rovo, specifically for customers using automation rules that invoke Rovo agents. Some customers may find that these automations are not completing as expected. We'll share updates here as more information becomes available.

  2. investigating Apr 14, 2026, 12:25 PM UTC

    We have identified that this incident also affects automation rules in Confluence that use Rovo agents. We are investigating and will provide updates as we learn more.

  3. identified Apr 14, 2026, 02:11 PM UTC

    We have identified the issue, and our teams are working to resolve it and restore normal operations as quickly as possible. We will provide further updates as they become available.

  4. monitoring Apr 14, 2026, 03:46 PM UTC

    The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability.

  5. resolved Apr 14, 2026, 04:11 PM UTC

    On April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Critical April 8, 2026

Multiple products impacted by search failures

Detected by Pingoru
Apr 08, 2026, 05:41 AM UTC
Resolved
Apr 08, 2026, 11:43 AM UTC
Duration
6h 2m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 14 updates

Read the full incident report →

Major March 10, 2026

Automation events delayed for some customers in the APAC region

Detected by Pingoru
Mar 10, 2026, 12:06 AM UTC
Resolved
Mar 10, 2026, 12:59 AM UTC
Duration
52m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
  1. investigating Mar 10, 2026, 12:06 AM UTC

    We are aware of customers experiencing delays with their automations within Jira, Jira Service Management, Jira Work Management, Jira Product Discovery and Confluence. Our team is investigating with urgency and we will provide an update within one hour.

  2. identified Mar 10, 2026, 12:15 AM UTC

    Our team has now identified the cause of this issue relating to delayed automation events and has put a hotfix in place to help restore automation performance. We will continue to monitor performance as the backlog of issues is now being processed.

  3. monitoring Mar 10, 2026, 12:51 AM UTC

    The performance degradation of automations has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

  4. resolved Mar 10, 2026, 12:59 AM UTC

    On 9 March UTC, Automation users in the APAC region may have experienced performance degradation within Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, Confluence. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Minor February 18, 2026

Groups are not clickable from Groups Page in Atlassian Administration

Detected by Pingoru
Feb 18, 2026, 10:57 AM UTC
Resolved
Feb 18, 2026, 11:30 AM UTC
Duration
32m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 3 updates
  1. investigating Feb 18, 2026, 10:57 AM UTC

    Org Admins are unable to click on any group from Groups page in Atlassian administration (admin.atlassian.com). Admins are unable to adding/removing users and app access from the groups while accessing from admin.atlassian.com. We are currently investigating the problem. Next update will be shared in 60 mins or sooner.

  2. monitoring Feb 18, 2026, 11:28 AM UTC

    We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

  3. resolved Feb 18, 2026, 11:30 AM UTC

    We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Read the full incident report →

Critical February 6, 2026

Disrupted JIRA and JSM availability

Detected by Pingoru
Feb 06, 2026, 08:24 PM UTC
Resolved
Feb 07, 2026, 05:38 AM UTC
Duration
9h 13m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 8 updates
  1. identified Feb 06, 2026, 08:24 PM UTC

    We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.

  2. identified Feb 06, 2026, 08:24 PM UTC

    Impact The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption. Current Status Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible. Next Steps The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

  3. identified Feb 06, 2026, 08:26 PM UTC

    We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.

  4. identified Feb 06, 2026, 10:33 PM UTC

    Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

  5. identified Feb 07, 2026, 02:22 AM UTC

    Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

  6. identified Feb 07, 2026, 03:43 AM UTC

    Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

  7. monitoring Feb 07, 2026, 05:28 AM UTC

    The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

  8. resolved Feb 07, 2026, 05:38 AM UTC

    On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Critical February 5, 2026

Some users in us-east-1 region unable to access Jira and JSM.

Detected by Pingoru
Feb 05, 2026, 02:13 PM UTC
Resolved
Feb 05, 2026, 09:38 PM UTC
Duration
7h 25m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 7 updates
  1. investigating Feb 05, 2026, 02:13 PM UTC

    Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same. We will provide update on the progress in next 60 minutes or sooner.

  2. identified Feb 05, 2026, 02:40 PM UTC

    Some users in the us-east-1 region cannot access Jira and JSM. We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution. We will provide update on the progress in next 60 minutes or sooner.

  3. identified Feb 05, 2026, 03:39 PM UTC

    We have identified the cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

  4. identified Feb 05, 2026, 05:35 PM UTC

    Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region. We will continue to share additional updates here as more information is available.

  5. identified Feb 05, 2026, 07:22 PM UTC

    Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation. We will continue to share additional updates here as more information is available.

  6. monitoring Feb 05, 2026, 09:09 PM UTC

    The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

  7. resolved Feb 05, 2026, 09:38 PM UTC

    On February 5, 2026, JIRA and JIRA Service Management experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Minor February 3, 2026

Confluence, Jira Mobile and Forge users may experience authentication issues

Detected by Pingoru
Feb 03, 2026, 10:19 AM UTC
Resolved
Feb 03, 2026, 10:50 AM UTC
Duration
30m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 3 updates
  1. investigating Feb 03, 2026, 10:19 AM UTC

    Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

  2. investigating Feb 03, 2026, 10:24 AM UTC

    Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

  3. resolved Feb 03, 2026, 10:50 AM UTC

    Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Read the full incident report →

Minor January 28, 2026

Degraded performance of Jira, JPD, and JSM in eu-west-1

Detected by Pingoru
Jan 28, 2026, 06:12 PM UTC
Resolved
Jan 28, 2026, 07:42 PM UTC
Duration
1h 30m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 3 updates
  1. identified Jan 28, 2026, 06:12 PM UTC

    We are actively investigating an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.

  2. identified Jan 28, 2026, 06:50 PM UTC

    We are continuing to investigate an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.

  3. resolved Jan 28, 2026, 07:42 PM UTC

    On Jan 28, 2026, Jira, Jira Product Discovery, and Jira Service Management users in eu-west-1 region may have experienced delays in viewing recently submitted updates on the web page and/or mobile apps. Updates continued to process successfully during the incident. There are no actions needed from customers. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →