Jira Core Outage History

Jira Core is up right now

Jira Core had 17 outages in the last 2 years totaling 113h 44m of downtime — averaging 0.7 incidents per month.

There were 17 Jira Core outages since October 15, 2025 totaling 113h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

Minor September 1, 2026

Jira - Work Item transition failures

Detected by Pingoru
Sep 01, 2026, 09:12 AM UTC
Resolved
Sep 01, 2026, 11:44 AM UTC
Duration
2h 31m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 3 updates
  1. investigating Sep 01, 2026, 09:12 AM UTC

    We are aware of an issue impacting Jira Work Item transitions. Affected users may experience errors when attempting to transition issues. Our teams are actively investigating the root cause. We will provide the next update in 60 minutes, or sooner if there is a material update.

  2. monitoring Sep 01, 2026, 10:11 AM UTC

    We have identified the root cause of the issue impacting Jira Work Item transitions and have applied a fix. We are currently seeing signs of recovery and will continue to monitor. We will provide the next update in the next 1 hour, or sooner if there is a material update.

  3. resolved Sep 01, 2026, 11:44 AM UTC

    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.

Read the full incident report →

Minor August 7, 2026

Degraded performance of JIRA

Detected by Pingoru
Aug 07, 2026, 01:26 AM UTC
Resolved
Aug 07, 2026, 01:46 AM UTC
Duration
19m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
  1. investigating Aug 07, 2026, 01:26 AM UTC

    We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.

  2. investigating Aug 07, 2026, 01:33 AM UTC

    We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.

  3. monitoring Aug 07, 2026, 01:39 AM UTC

    The performance degradation of JIRA 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 Aug 07, 2026, 01:46 AM UTC

    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.

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 →

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 →

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 December 15, 2025

Degraded performance of Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo

Detected by Pingoru
Dec 15, 2025, 04:26 PM UTC
Resolved
Dec 15, 2025, 07:02 PM UTC
Duration
2h 35m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
  1. identified Dec 15, 2025, 04:26 PM UTC

    We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, and Rovo. We'll share updates here as more information is available.

  2. identified Dec 15, 2025, 04:47 PM UTC

    We have identified the cause of the issue, and our teams are diligently working on mitigations. We're currently seeing signs of improvements. We'll continue to share additional updates here in 60 minutes or as more information becomes available.

  3. identified Dec 15, 2025, 05:47 PM UTC

    Our teams are continuing to implement mitigations. Error rates have decreased across all products and we are seeing improvements. We will continue to provide updates here in 60 minutes or as more information becomes available.

  4. resolved Dec 15, 2025, 07:02 PM UTC

    On December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced performance degradations and errors on the web page and mobile apps. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Minor December 1, 2025

Degraded Performance for Some Jira Users

Detected by Pingoru
Dec 01, 2025, 05:24 PM UTC
Resolved
Dec 01, 2025, 06:26 PM UTC
Duration
1h 2m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 5 updates
  1. investigating Dec 01, 2025, 05:24 PM UTC

    We are investigating an incident affecting Jira Work Management, Jira, and Jira Service Management. We will provide updates via Statuspage shortly. The ability to view issues and boards is experiencing degraded performance for some users. Customers may notice a slowdown in accessing these functionalities.

  2. investigating Dec 01, 2025, 05:26 PM UTC

    We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

  3. investigating Dec 01, 2025, 05:30 PM UTC

    We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

  4. investigating Dec 01, 2025, 06:26 PM UTC

    We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

  5. resolved Dec 01, 2025, 06:26 PM UTC

    Impact Jira Software users experienced degraded performance affecting their ability to view issues and boards. Users may have encountered an error or slowdown during this time. Current Status The situation is currently mitigated due to actions taken on the affected systems, leading to a stabilization of services. Next Steps The team is actively monitoring the systems.

Read the full incident report →

Major November 15, 2025

Some users are unable to send emails from Jira

Detected by Pingoru
Nov 15, 2025, 04:29 PM UTC
Resolved
Nov 17, 2025, 11:50 AM UTC
Duration
1d 19h
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
  1. identified Nov 15, 2025, 04:29 PM UTC

    We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

  2. identified Nov 15, 2025, 09:36 PM UTC

    We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

  3. monitoring Nov 15, 2025, 09:36 PM UTC

    We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users. After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal. We apologize for any inconvenience this may have caused.

  4. resolved Nov 17, 2025, 11:50 AM UTC

    The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Read the full incident report →

Major October 27, 2025

Jira Platform Incident - viewIssue and createIssue Service Disruption

Detected by Pingoru
Oct 27, 2025, 04:33 PM UTC
Resolved
Oct 27, 2025, 05:50 PM UTC
Duration
1h 16m
Affected: Viewing content
Timeline · 2 updates
  1. investigating Oct 27, 2025, 04:33 PM UTC

    Impact Jira Software users are experiencing service degradation in viewIssue and createIssue. This issue affects multiple regions, with noticeable impacts on user functionalities across these experiences. This is potentially affecting Jira Service Management and Jira Work Management. Next Steps - The team is investigating and further communications will be provided in 60 minutes.

  2. resolved Oct 27, 2025, 05:50 PM UTC

    Between 15:09 UTC to 17:16 UTC, some customers experienced partial outage for Jira Work Management, Jira Service Management, and Jira viewIssue, createIssue and editIssue caused by a faulty code rollout. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The root cause is still being investigated and will be provided in the post incident review. The conditions that cause the errors are being addressed and we're actively working on a permanent fix. The issue has been resolved and the services are operating normally.

Read the full incident report →

Major October 20, 2025

Atlassian Cloud Services impacted

Detected by Pingoru
Oct 20, 2025, 07:56 AM UTC
Resolved
Oct 21, 2025, 05:24 AM UTC
Duration
21h 28m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 25 updates

Read the full incident report →

Minor October 15, 2025

Unable to perform UI Operations

Detected by Pingoru
Oct 15, 2025, 01:43 PM UTC
Resolved
Oct 15, 2025, 04:16 PM UTC
Duration
2h 32m
Affected: Automation for Jira
Timeline · 4 updates
  1. investigating Oct 15, 2025, 01:43 PM UTC

    UI based Customer interactions are currently degraded and our team is actively investigating the same. We shall keep you informed of the progress in next 2 hours.

  2. investigating Oct 15, 2025, 02:34 PM UTC

    Atlassian team is actively investigating the issue with UI based Customer interactions. Existing automation rules continue to run without any issue. Accessing automation rules and creating new automation rules could lead to intermittent failures. We shall keep you informed of the progress in next 2 hours, if not sooner.

  3. monitoring Oct 15, 2025, 03:26 PM UTC

    We have recovered from a issue which saw degraded Automation experience. Impact Some Customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Current Status The incident has been mitigated and we continue to investigate the cause of this incident Next Steps We are continuing to monitor the service, and will provide further updates in the next two hours

  4. resolved Oct 15, 2025, 04:16 PM UTC

    Between 14:00 UTC to 16:00 UTC, we experienced automation rule functionality degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. Impact Some customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Approximately 50 percent of Automation API calls were affected in the us-east-1 region with customers receiving 429 status codes. Current Status The incident has been mitigated by increasing the API Gateway rate limit service quota and disabling the internal service that was causing high traffic volume. Next Steps We are conducting a root cause analysis of the internal service. A post incident review will be conducted.

Read the full incident report →