Jira
Apps and SaaS. Source: Jira status page.
- Incidents, last 90 days
- 14
- Median to mitigation
- 55m
- Median to resolution
- 2h 15m
- p95 to resolution
- 10h 50m
- Naming an upstream provider
- 0%
- With a postmortem on the status page
- 28%
What failed, last 90 days
| The text does not say enough to tell | 8 |
| Exhausted memory, disk, CPU, queues, connection pools or quotas | 2 |
| A configuration change caused the failure | 1 |
| A provider or third-party service this vendor depends on failed | 1 |
| A code release introduced the failure | 1 |
| A zone, region or data center became unavailable | 1 |
Tagged by deepseek/deepseek-v4.1-flash from each incident's updates. See the methodology.
Incidents per month
All recorded incidents
Jira - Project Sidebar Loading Degradation
Affected: Viewing content
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating an issue impacting the project sidebar and navigation in Jira Cloud. Users may encounter timeouts or missing menus when attempting to access project views. Teams are actively analyzing telemetry to identify a mitigation. We will provide our next update in 60...
-
monitoring
Mitigations are in place and we are seeing recovery across Jira Cloud navigation services. Project sidebars are now loading as expected. Our teams continue to monitor the situation, and we expect to confirm full resolution in our next update in 1 hour or sooner.
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Job processing and scheduling is degraded affecting multiple Atlassian products
Affected: Notifications, Automation for Jira
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud. Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and...
-
identified
Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.
-
identified
Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.
-
identified
Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service...
-
identified
Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be...
-
resolved
On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for...
-
postmortem
### 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...
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded Performance Viewing Issues and Boards
Affected: Viewing content, Create and edit
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We continue to investigate the issue impacting Jira issue creation, issue viewing, and board loading. Our teams remain engaged on identifying a resolution. We will provide the next update in 1 hour, or sooner if there is material progress.
-
monitoring
Mitigations have been deployed and we are seeing positive signs of recovery across Jira. Issues viewing work items, loading boards, and creating tickets are subsiding. We are continuing to monitor system health to ensure full stability and will share our next update within 60...
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded Performance Accessing Jira
Affected: Viewing content
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
-
monitoring
We have been tracking an issue impacting Jira where users may have encountered errors or degraded performance accessing Jira and viewing issues. Mitigations are in place and we are seeing positive signs of recovery. Our teams are continuing to monitor the situation, and we...
-
monitoring
We are continuing to closely monitor the situation to ensure full stability across Jira. Recovery signs remain steady. Our next update will be shared in 60 minutes, or sooner.
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance affecting Jira Software and Jira Service Management
Affected: Viewing content
Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of an issue affecting Jira Software and Jira Service Management. Affected users may experience errors or delays when loading issue views and viewing boards. We are working to identify the root cause and will provide an update as more information...
-
monitoring
A mitigation has been deployed, and we are observing recovery across Jira Software and Jira Service Management issue views and boards. Our engineering teams are closely monitoring the environment to ensure sustained stability. We will provide another update once full resolution...
-
resolved
On 11 September 2026, Between 07:02 UTC and 07:56 UTC, some Jira Software and Jira Service Management users may have experienced degraded performance and errors when accessing Work Items and Boards. The issue has now been resolved, and all services are operating normally.
-
postmortem
### 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...
Excerpts are shortened. Read the full incident on Jira's status page.
Disrupted JIRA availability in US East
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
-
investigating
We are actively investigating reports of a service disruption affecting JIRA customers in US East. We will share updates here as more information is available.
-
monitoring
Our teams have taken mitigation steps to reduce the impact and recovery among affected customers began at 16:15 UTC. We continue to investigate the root cause of the issue, and will share additional updates here as more information is available.
-
resolved
On September 3, 2026, JIRA 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.
-
postmortem
### 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,...
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance of JIRA
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are actively investigating reports of performance degradation affecting forms functionality. We will share updates here as more information is available.
-
identified
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience forms not working as expected. We will continue to share additional updates here as more information is available.
-
identified
Our teams continue to work on the mitigation. We will continue to share additional updates here as more information is available.
-
monitoring
The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Jira - Work Item transition failures
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
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.
-
monitoring
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.
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Fetching mails from Microsoft accounts producing errors and preventing email based creation of Jira work items
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
identified
Impact
-
monitoring
Jira Incoming Emails are experiencing elevated failures when fetching mail from Microsoft accounts. This affects email-based creation and updates of Jira work items. Users may see 500 internal server errors when email fetch attempts occur. We are tracking updates from Microsoft...
-
resolved
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...
Excerpts are shortened. Read the full incident on Jira's status page.
Issues accessing multiple Atlassian products in some regions
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
Our teams have identified this issue is also impacting Jira Service Management. We will update further as soon as possible.
-
investigating
We are investigating an issue with accessing products that is impacting Confluence, Jira Cloud and Jira Serivce Management customers. Our team is urgently investigating this issue and we will provide further details within one hour or sooner if information is available.
-
identified
Our teams have identified a possible fix for the issues impacting Jira Cloud, Jira Service Management and Confluence. This is now being rolled out to impacted regions and we will update within one hour, or sooner if further information is available.
-
monitoring
The issues relating to loading Jira Cloud, Jira Service Management and Confluence are now in recovery. We'll continue to monitor closely to confirm stability and provide an update within one hour, or sooner as more information becomes available.
-
resolved
On 27 August 2026 UTC, Atlassian products including Jira Cloud, Jira Service Management and Confluence 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. A...
-
postmortem
**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...
Excerpts are shortened. Read the full incident on Jira's status page.
Notifications are delayed
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
-
investigating
We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and slack notifications for Jira, JSM and Confluence. Our teams are investigating the issue and more information will be shared within the next 1 hour.
-
investigating
Our teams have identified the impacted regions and are actively working to mitigate the issue. We will provide further updates within an hour, or sooner if we have significant progress to share.
-
investigating
Our teams have taken few corrective measures to mitigate the issue in one of the impacted regions and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates...
-
monitoring
Our teams continue to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant...
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance of Notifications
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will share updates here as more information is available.
-
investigating
Our teams have identified three impacted regions, and continue to investigate the increased latency affecting email, mobile, and Slack notifications for JIRA, JSM, and Confluence.
-
identified
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience increased latency in email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will continue to share additional updates here as...
-
resolved
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...
Excerpts are shortened. Read the full incident on Jira's status page.
Performance and access related issues with Jira
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
-
investigating
We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.
-
monitoring
Some customers experienced issues accessing affected services in the Central European region. We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to...
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance of JIRA
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
-
investigating
We are actively investigating reports of performance degradation affecting JIRA. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
-
investigating
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.
-
investigating
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.
-
monitoring
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.
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance of Jira Automation rules
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are actively investigating reports of performance degradation affecting Automation rules for Jira and Jira Service Management. We will share updates here as more information is available.
-
investigating
Our teams are continuing to investigate delays in Jira and Jira Service Management automation rule executions for some customers. We are seeing signs of improvement, but affected users may still experience delays. We'll share updates here as more information is available.
-
identified
The team has identified a root cause and after initial testing, is now enacting scaling changes to help to prevent these rule execution delays. We'll monitor performance over the next 24 hours and provide an update at that time or sooner if we can confirm the improvement is in...
-
resolved
Our team has been able to validate that all rule executions are performing normally and this issue is now resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance of Jira Automation rules
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are actively investigating reports of performance degradation affecting Automation rules for Jira and Jira Service Management. We will share updates here as more information is available.
-
identified
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. We are currently seeing signs of improvements, however, affected users may experience delays in Jira and Jira Service management Automation rule executions. We'll continue to...
-
resolved
On July 20, 2026, some Jira and Jira Service Management users 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.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance of JIRA Automation
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are actively investigating reports of performance degradation affecting Automation for JIRA. We will share updates here as more information is available.
-
investigating
We continue to investigate performance degradation affecting Automation for JIRA in Europe regions. We will share updates here as more information becomes available.
-
identified
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience performance degradation affecting Automation for JIRA in Europe regions. We will continue to share additional updates here as more information is...
-
monitoring
The performance degradation of Automation for JIRA in Europe regions has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.
-
resolved
On July 6, 2026, some users in Europe regions may have experienced performance degradation with Automation for JIRA. The issue has now been resolved, and the service is operating normally for all affected customers. If you believe the issue continues to persist, please contact...
-
postmortem
## Summary On Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker, and related workflows. The incident began when a core identity...
Excerpts are shortened. Read the full incident on Jira's status page.
Reliability issues with Jira and Confluence
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.
-
monitoring
We have successfully applied the fix and are seeing recovery. Automation capabilities are being restored and should operate normally going forward. Data processing requests submitted during the outage period were not completed due to service unavailability. We continue to...
-
investigating
We are still seeing some issues with user-search, user-picker and assets across with the EU-Region. We continue to investigate the situation and will provide additional updates in the next one hour or sooner.
-
monitoring
We have applied the fix to mitigate the issue and are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.
-
resolved
On July 6th 2026, between 06:51 UTC to 09:39 UTC some users may have experienced issues related Automation, and between 08:10 UTC to 11:50 UTC some users may have experienced issues related to user-search, user-picker and assets in the EU-Region. The issues have now been...
-
postmortem
## Summary On Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker, and related workflows. The incident began when a core identity...
Excerpts are shortened. Read the full incident on Jira's status page.
Jira : Incoming emails partial outage
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
monitoring
Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft...
-
resolved
Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still...
Excerpts are shortened. Read the full incident on Jira's status page.
Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
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...
-
identified
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...
-
monitoring
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...
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Some users experiencing issues viewing boards and work items
Affected: Viewing content
-
investigating
We are investigating reports of intermittent errors and degredated performance for some Jira Service Management and Jira Cloud customers. We will provide further updates within one hour.
-
identified
Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the...
-
identified
Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the...
-
identified
Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the...
-
identified
Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the...
-
identified
Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the...
-
identified
Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the...
-
monitoring
Our team has been able to apply the fix and mitigate the issue. The services have been restored to normal operations. We will continue to actively monitor over the next 8 hours to confirm stability.
-
resolved
The issue has now been resolved, and the service is operating normally for all affected customers.
Excerpts are shortened. Read the full incident on Jira's status page.
Users experiencing issues loading work items in Jira and JSM
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration
-
investigating
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.
-
identified
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.
-
resolved
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...
Excerpts are shortened. Read the full incident on Jira's status page.
Users experiencing issues loading work items in Atlassian products
Affected: Viewing content, Create and edit
-
investigating
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.
-
monitoring
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.
-
resolved
The issues relating to viewing and creating work items in Jira should now be fully resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance of Jira and JSM automations in US East
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
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.
-
resolved
On June 2, 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...
Excerpts are shortened. Read the full incident on Jira's status page.
For Jira-software viewIssues and viewBoard are degraded
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
We are investigating cases of partial-outage for Jira-software in the EU Region. We will provide more details within the next hour.
-
identified
We have identified an issue causing degraded performance for Jira Software, Jira Work Management, and Jira Service Management in the EU region. affected users may experience 5XX errors when accessing issues, boards, and navigation. Our engineering team is actively working on a...
-
monitoring
We have implemented a fix for the issue causing degraded performance for Jira Software and Jira Service Management in the EU region. The impact has been mitigated, and we are actively monitoring the stability.
-
resolved
This incident has been resolved. The issue causing degraded performance for Jira Software and Jira Service Management in the EU region has been fully mitigated. We have deployed a fix to prevent recurrence. If you continue to experience issues, please contact Atlassian Support....
-
postmortem
**SUMMARY** On June 01, 2026, between 06:54 and 08:28 UTC, Atlassian customers using Jira, Jira Service Management, and Jira Work Management were unable to view issues, boards, and backlogs, and experienced errors when performing transitions, adding comments, and navigating the...
Excerpts are shortened. Read the full incident on Jira's status page.
Forge custom fields are not getting created
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
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.
-
investigating
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.
-
identified
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,...
-
resolved
The root cause has been identified and a fix has been applied. Full service restoration has been completed.
Excerpts are shortened. Read the full incident on Jira's status page.
Users experiencing issues accessing multiple Atlassian products
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more...
-
investigating
We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is...
-
identified
Further confirmations of impacted products have now been added to the incident. Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.
-
identified
It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team...
-
identified
Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products. At this time, Atlassian customers should also be able to once again raise support requests with our team. We will provide further update...
-
monitoring
Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken...
-
monitoring
We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been...
-
monitoring
We are approaching full system recovery at this time, and are performing final confirmations that services are restored.
-
resolved
All products and services impacted by this incident should now be fully recovered, and this incident is resolved.
-
postmortem
### Summary On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback...
Excerpts are shortened. Read the full incident on Jira's status page.
Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some users
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.
-
identified
Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further...
-
identified
The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update...
-
identified
Our team has been able to confirm that new automation events should now be processed correctly. We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.
-
identified
While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident. We will provide an update on the progress within one hour.
-
identified
Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.
-
resolved
We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.
-
postmortem
### Summary ### On May 12, 2026 between 19:01 and 20:46 UTC, a subset of Atlassian customers may have experienced delays in background operations and automation processes. Some background operations, such as notifications or search indexing, were delayed until May 14, 2026 19:25...
Excerpts are shortened. Read the full incident on Jira's status page.
Multiple Atlassian services are experiencing issues
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.
-
identified
We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.
-
identified
We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.
-
identified
Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.
-
identified
We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.
-
identified
Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.
-
identified
We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each...
-
monitoring
The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation...
-
monitoring
We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.
-
monitoring
Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We...
-
resolved
On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.
-
postmortem
All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded...
Excerpts are shortened. Read the full incident on Jira's status page.
Jira users unable to log time while on business board
Affected: Create and edit
-
investigating
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.
-
identified
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.
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
The Work Item view experience of Jira is restored
Affected: Viewing content, Create and edit
-
investigating
We are investigating an incident affecting Jira Software (viewBoard, viewIssue, createIssue). Our team is working to identify the cause and restore service to normal levels. We will provide the next update within 60 minutes.
-
investigating
We are actively investigating reports of a service disruption affecting the issue viewing experience in Jira. This is also impacting the accessibility of support tickets. We will share updates here as more information becomes available.
-
investigating
We are actively investigating reports of a service disruption affecting the Work Item viewing experience in Jira. This is also impacting the accessibility of support tickets. We will share updates here as more information becomes available.
-
resolved
The Jira Work Item View experience has been restored to normal service. Our teams are continuing to investigate the root cause affecting this issue. We will provide more details once we identify the root cause
-
postmortem
### SUMMARY ### Between May 1, 2026 at 23:34 UTC and May 2, 2026 at 02:53 UTC Atlassian customers using Jira and Jira Service Management (JSM) across all Cloud tenants received an error page when attempting to open a work item due to a schema incompatibility, and editing work...
Excerpts are shortened. Read the full incident on Jira's status page.
Delays in Jira webhook delivery
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
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.
-
identified
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.
-
monitoring
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.
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Disrupted Rovo availability for Automation rules
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
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...
-
investigating
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.
-
identified
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.
-
monitoring
The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability.
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Users experiencing issues with login across Atlassian products
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
monitoring
Our team is aware that some users were unable to log in to Atlassian products with their Atlassian accounts. While we believe this issue is now resolved, we are continuing to monitor all products and services for any ongoing impact. Our team is investigating with urgency, and we...
-
monitoring
Atlassian account login services are now operating as expected, and we are not observing new errors. We continue to closely monitor our systems to ensure they remain stable. We will provide another update within 60 minutes or sooner if we detect a change in status.
-
resolved
On April 13, 2026, between 05:49 a.m. and 06:25 a.m. UTC, some users were unable to log in to Atlassian products with their Atlassian accounts. The underlying issue has been addressed, and authentication services have remained stable with no new impact observed.
-
postmortem
### Summary On April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed...
Excerpts are shortened. Read the full incident on Jira's status page.
Multiple products impacted by search failures
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.
-
investigating
Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.
-
investigating
The impact of this incident is now understood to also be impacting search in Jira and Confluence, as well as additional downstream impacts to Rovo Chat, User Management, Administration and Guard. Our team is continuing to investigate with urgency and we will provide further...
-
investigating
Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.
-
investigating
Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.
-
identified
We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a...
-
identified
We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a...
-
identified
Confluence and Jira search reliability is improving, and we expect full recovery shortly; we will continue to closely monitor the services to ensure they remain stable.
-
identified
We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a...
-
identified
We have restored core search functionality and services are operating again, but some customers may still experience delays when searching for data changed within the last hour while new data continues to be indexed. We are actively working to complete reindexing and will update...
-
identified
We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a...
-
monitoring
The issue has been resolved, and services are now operating normally. Some customers may still experience delays when searching for data changed within the last hour, while new data continues to be indexed. We'll continue to monitor closely to confirm stability.
-
resolved
The issue has now been resolved, and the service is operating normally for all affected customers.
-
postmortem
### Summary On April 8, 2026, between 04:46 UTC and 12:09 UTC, search functionality was unavailable or degraded across several Atlassian Cloud products, including Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and...
Excerpts are shortened. Read the full incident on Jira's status page.
Automations aren't triggering on work item creation, field updates, or comment additions
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.
-
investigating
Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.
-
investigating
Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more...
-
investigating
We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.
-
investigating
We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.
-
monitoring
We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.
-
monitoring
We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.
-
monitoring
We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.
-
monitoring
Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.
-
resolved
The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within...
-
postmortem
### Summary On March 18, 2026, between 10:06 and 13:47 UTC, customers experienced delays in Automation rules executing when triggered by Jira events such as Work Item creation, Work Item updates, and comments. Automation rules using other trigger types, including scheduled...
Excerpts are shortened. Read the full incident on Jira's status page.
Automation events delayed for some customers in the APAC region
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
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.
-
identified
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.
-
monitoring
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.
-
resolved
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...
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance of Cloud Products when selecting users or teams
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites. We will share updates here as more information is available.
-
investigating
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information...
-
identified
Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites.
-
identified
We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more...
-
identified
Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites. We anticipate next update to be posted in approximately 8 hours.
-
identified
Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately. We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards...
-
identified
Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be...
-
identified
We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users...
-
identified
We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users...
-
resolved
This issue has been resolved and all services are functional.
Excerpts are shortened. Read the full incident on Jira's status page.
Groups are not clickable from Groups Page in Atlassian Administration
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
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...
-
monitoring
We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.
-
resolved
We have implemented the fix and the group page in the Admin Hub is now functioning as expected.
Excerpts are shortened. Read the full incident on Jira's status page.
Increased error rates on Jira and Jira Service Management Ecosystem Apps
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
We are investigating an issue with Increased error rates on APIs in Jira and Jira Service Management Ecosystem Apps. We will continue to share additional updates here as more information is available. Forge and Connect apps are not affected.
-
investigating
Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.
-
identified
We have identified the cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience increased error rates on APIs in Jira and Jira Service Management Ecosystem Apps.
-
identified
Our teams identified two fix paths: a quick fix and a longer, time-consuming fix. We will test the quick fix over the weekend and, if no issues arise, implement it on Monday. We will provide the next update on Monday, Feb 16, 2026.
-
identified
Impact Ecosystem, Jira, and Jira Service Management customers might experience API call failures when using OAuth 2.0 apps, receiving 'The app is not installed on this instance' errors. The incident is attributed to OAuth scope mismatches between different internal services....
-
identified
Our teams have identified customers that are actively experiencing issues relating to loss of access to their apps, and we are progressively rolling out a fix to these customers with urgency. We will provide further update within 24 hours or sooner if available.
-
identified
Our team is continuing to work on correcting the impact from this issue. A tested and validated process is now running to restore affected apps and our team is closely monitoring traffic to help to rule out any issues. Please raise a support request if you require further...
-
monitoring
Our team has resolved the permission errors relating to this incident across all Apps, and we will continue to monitor for any unexpected issues. For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be...
-
monitoring
This issue is resolved. In our monitoring no other unexpected issues were seen. For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.
-
resolved
This issue is resolved. In our monitoring no other unexpected issues were seen. For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.
Excerpts are shortened. Read the full incident on Jira's status page.
Disrupted JIRA and JSM availability
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Names an upstream provider: AWS.
-
identified
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.
-
identified
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...
-
identified
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.
-
identified
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.
-
identified
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.
-
identified
Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.
-
monitoring
The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Some users in us-east-1 region unable to access Jira and JSM.
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Names an upstream provider: AWS.
-
investigating
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.
-
identified
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.
-
identified
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.
-
identified
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.
-
identified
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.
-
monitoring
The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Confluence, Jira Mobile and Forge users may experience authentication issues
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
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...
-
investigating
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...
-
resolved
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.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance of Jira, JPD, and JSM in eu-west-1
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
identified
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.
-
identified
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...
-
resolved
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...
Excerpts are shortened. Read the full incident on Jira's status page.
Issue affecting Assets
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
Impact Users of the Assets product are experiencing intermittent accessibility issues, resulting in gateway timeouts and internal server errors. These technical disruptions are causing difficulties in performing queries, which may manifest as slow performance or failure to load...
-
investigating
We continue to investigate the issue, and next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.
-
monitoring
The performance degradation of Assets has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
-
resolved
On January 20, 2026, some customers may have experienced performance degradation of Assets. The issue has now been resolved, and the service is operating normally for all affected customers.
Excerpts are shortened. Read the full incident on Jira's status page.
Disrupted create and view issue for some customers
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
We are actively investigating reports of a partial service disruption affecting Jira create, view, view board, and edit issue for some customers. We'll share updates here as more information is available.
-
investigating
We are continuing to actively investigate reports of a partial service disruption affecting Jira create issue, issue view, view board, and edit issue for some customers. We'll share updates here in one hour or as more information is available.
-
investigating
Our teams are continuing to actively investigate reports of a partial service disruption affecting Jira create issue, issue view, view board, and edit issue for some customers. We'll share updates here in one hour or as more information is available.
-
investigating
Our teams are continuing to actively investigate reports of a partial service disruption affecting Jira create issue, issue view, view board, and edit issue for some customers. We'll share updates here in one hour or as more information is available.
-
monitoring
The issue has been resolved and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.
-
resolved
The service disruption has been fully resolved, and services are now operating normally for all impacted customers.
Excerpts are shortened. Read the full incident on Jira's status page.
Disrupted Automation for Jira triggers not running for some customers
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
We are investigating an incident impacting Automation for Jira across Jira and Jira Service Management. Some automation rules that use specific triggers may fail to execute. Our team is working to identify the cause and restore normal service. We will provide the next update...
-
identified
We have identified the cause of the issue, and our teams are diligently working on a mitigation. We will continue to share additional updates here as more information becomes available.
-
identified
Our engineers are continuing work toward the resolution of the incident impacting Automation for Jira. There are no new updates to share at this time. We will provide the next update within 2 hours.
-
identified
Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. We have...
-
identified
Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. The cause...
-
monitoring
Issue has been fixed for all new events - we are waiting for confirmation from some customers when they come online. Customers using Jira and Jira Service Management in Asia Pacific and South East regions had faced issues with Automation for Jira. Other regions not impacted....
-
monitoring
We are currently replaying historical events for affected customers to rerun Automation for Jira rules that failed to execute earlier. Our teams are closely monitoring the results of this replay to confirm that all affected automations are running as expected. We will provide...
-
monitoring
We have replayed about 7 hours of historical events for affected customers to rerun Automation for Jira rules that previously failed. This covers most of the APAC business hours. Based on customer feedback, our team continues monitoring the situation and plans to complete...
-
resolved
Rerunning the remaining Automation for Jira rules that failed for affected customers is complete. This update resolves the issue.
Excerpts are shortened. Read the full incident on Jira's status page.
Outbound Email, Mobile Push Notifications, and Support Ticket Delivery Impacting All Cloud Products
Affected: Notifications
-
monitoring
We have taken steps to mitigate the issue and are seeing recovery in the affected services. Our teams will continue to closely monitor the situation and are actively working to confirm that all services are fully restored. We will provide further updates as we make additional...
-
resolved
We have successfully mitigated the incident and all affected services are now fully operational. Our teams have verified that normal functionality has been restored across all areas. Thank you for your patience and understanding while we worked to resolve this issue.
-
postmortem
### Summary On **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence functionality remained available. The issue was triggered when **TLS...
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance of Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
identified
We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo. We'll share updates here as more information is available.
-
identified
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.
-
identified
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.
-
identified
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.
-
resolved
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....
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded Performance for Some Jira Users
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
-
investigating
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...
-
investigating
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.
-
investigating
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.
-
investigating
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.
-
resolved
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,...
Excerpts are shortened. Read the full incident on Jira's status page.
Multiple Atlassian services experiencing degraded performance
Affected: Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Names an upstream provider: GitHub.
-
investigating
Multiple Atlassian services are seeing outages and we are investigating the same. We shall keep you posted on the progress in 60 minutes, if not sooner
-
investigating
Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.
-
monitoring
The Trello performance degradation affecting some customers has been resolved. A subset of customers may have experienced intermittent errors on some of our other products, but these should also now be resolved too. We'll continue to monitor closely to confirm stability.
-
resolved
The Trello performance degradation has been resolved. Also, some intermittent errors on some of our other products, has also now been resolved. The issue has now been resolved, and the service is operating normally for all affected customers.
-
postmortem
### Summary On November 21, 2025, between 13:44 and 15:16 UTC, Trello customers were intermittently unable to view and update data on their boards. Customers also may have experienced issues authenticating with Atlassian products, and creating new GitHub and Slack integrations....
Excerpts are shortened. Read the full incident on Jira's status page.
Custom Fields loses values after submission on Issue Create Screen
-
resolved
On 20 November 2025, affected Jira users may have experienced some service disruption for Forge custom fields on Jira issue create. The issue has now been resolved, and the service is operating normally for all affected customers.
Excerpts are shortened. Read the full incident on Jira's status page.
Forge Custom Fields loses value after submission on Issue Create Screen
-
resolved
On 20 November 2025, affected Jira users may have experienced some service disruption for Forge custom fields on Jira issue create. The issue has now been resolved, and the service is operating normally for all affected customers.
Excerpts are shortened. Read the full incident on Jira's status page.
Customers are receiving message NO SUCH TRACK intermittently when opening Jira issues
-
resolved
On November 18, 2025, some Jira users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.
Excerpts are shortened. Read the full incident on Jira's status page.
Some users are unable to send emails from Jira
-
resolved
The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance and intermittent errors
-
resolved
On November 3, 2025, some Confluence, Jira Service Management, and Jira Cloud users may have experienced performance degradation and errors in the Global Automation UI page. Automation executions were not impacted by this incident. The issue has now been resolved, and the...
Excerpts are shortened. Read the full incident on Jira's status page.
Automation rule conditions order change is affecting customers
-
resolved
Confirmed that the incident has been resolved and the automation rules are executing as expected.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance of Atlassian cloud sites for some customers
-
resolved
Incident has been resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Jira Platform Incident - viewIssue and createIssue Service Disruption
-
resolved
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...
Excerpts are shortened. Read the full incident on Jira's status page.
Some users experiencing 'Something went wrong error' message in Jira and JSM
-
resolved
Our team identified a problematic feature release that was causing the 'something went wrong' errors to appear within Jira and Jira Service Management. We disabled the feature that was causing this issue and normal services within Jira and Jira Service Management are now fully...
Excerpts are shortened. Read the full incident on Jira's status page.
Delay in execution of Automation rules
Names an upstream provider: AWS.
-
resolved
Our teams have identified and fixed the root cause of the issue that caused delay in executing Automation rules. This was caused due to scaling issues following on from the recent AWS outage. This issue is marked as resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Atlassian Cloud Services impacted
-
resolved
Our team is now able to see full recovery across the vast majority of Atlassian products. We are aware of some ongoing issues with specific components such as migrations and JSM virtual service agents, and our team is continuing to investigate with urgency. We apologise for the...
Excerpts are shortened. Read the full incident on Jira's status page.
Unable to perform UI Operations
Names an upstream provider: AWS.
-
resolved
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...
Excerpts are shortened. Read the full incident on Jira's status page.
Error message in Jira when working on issues. Error code Hash 4G7N40
-
resolved
Our team actively investigated the incident impacting Jira, and immediately identified the root cause and implemented steps to restore the affected services.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance to multiple Atlassian experiences
-
resolved
A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.
Excerpts are shortened. Read the full incident on Jira's status page.
Xray Testing board fails to load
-
resolved
Xray team after deep dive on their end have confirmed to Atlassian that the cause of the this issue is at their end and they are working on fixing the same. With this update from Xray team, Atlassian is considering this issue closed since there is no issue at Atlassian end.
Excerpts are shortened. Read the full incident on Jira's status page.
Duplicate issues being created in Jira Service Management and Jira
-
resolved
Duplicated message. Please refer to the updates from this incident: https://jira-software.status.atlassian.com/incidents/knx11cj542ks
Excerpts are shortened. Read the full incident on Jira's status page.
Duplicate issues being created in Jira Service Management and Jira
-
resolved
Our team has completed restoration of customer environments for the vast majority of those impacted by this issue. We will continue working with the final impacted customers to ensure we reach a full resolution. If you are still experiencing any issues relating to these...
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance in Confluence and Jira for Microsoft Edge users
-
resolved
An update has been released by Microsoft to resolve this issue for users of the Edge browser. To verify that you are running the required version of Edge, you can navigate to edge://components/ in the address bar, click the 'Check for update' button for the 'Trust Protections...
Excerpts are shortened. Read the full incident on Jira's status page.
Disappearing 'account' field for Tempo users
-
resolved
Our team is now satisfied that the issues relating to these missing fields are now resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Users receiving 'something went wrong' or 'Hash MHHY91' Error messages when using Apps
-
resolved
Our team has continued to monitor the errors relating to accessing Apps and we are now satisfied that this issue is fully resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Delays in automation rules execution
-
resolved
Between09:13 am UTC to 01:58 pm UTC, we experienced delays in Automation rules execution for Jira Service Management and Jira. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Users experiencing issues loading Kanban boards in Jira
-
resolved
The issue relating to a 'Something went wrong' error message appearing on Kanban boards should now be resolved. For any users that are still experiencing the issue please ensure that you refresh your browser window multiple times which should restore the board functionality.
Excerpts are shortened. Read the full incident on Jira's status page.
Custom Fields loses values after submission on Global Issue Create Screen
-
resolved
Between 02:00 am UTC and 11:57 am UTC, we experienced issues with custom fields created by the Forge app for Jira Work Management and Jira. The issue has been resolved, and the service is now operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Product invitation emails not being correctly sent to users
-
resolved
Between 2025-08-03T21:34 and 2025-08-05T03:43 UTC some users would not have received the emails for product invitations. The change that caused these emails to stop being sent has been rolled back. New invitation emails should now be sent correctly for all products. For users...
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded experience adding and accessing media attachments
-
resolved
We have resolved the issue impacting adding/accessing media attachments across products. We will continue to monitor the situation.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded experience adding and accessing attachments for issues
-
resolved
We have resolved this issue and are continuing to monitor the situation.
Excerpts are shortened. Read the full incident on Jira's status page.
Delays in automation rules execution
-
resolved
Between <15:34 UTC> to <18:42 UTC>, we experienced delays in Automation rule execution for Jira Service Management and Jira. The issue has been resolved and the service is operating normally. All new rule submissions are executed normally. For the old (backlog) rules, the system...
Excerpts are shortened. Read the full incident on Jira's status page.
Issues loading Jira pages for some users
-
resolved
Our team identified an issue that was intermittently causing pages to load as blank for some users between 00:22 UTC and 01:45 UTC. Our team has now deployed a fix and this issue is resolved. We apologise for any inconvenience caused by this issue.
Excerpts are shortened. Read the full incident on Jira's status page.
Intermittent failure in Forge app invocation
-
resolved
Between 10th July 5:44 am UTC to 7:44 am UTC, we experienced intermittent failure in some app funstionality(smart links, scheduled triggers) for Confluence, Jira Work Management, Jira Service Management, Jira, and Compass. The issue has been resolved and the service is operating...
Excerpts are shortened. Read the full incident on Jira's status page.
Issues affecting user syncing, Atlassian Administration
-
resolved
Between 07:40 UTC and 10:31 UTC, we experienced issues affecting user syncing in Atassian Administration. This affected Confluence, Jira Work Management, Jira Service Management, Jira, Trello, and Guard. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Users unable to open their Jira cloud products
-
resolved
The issue affecting Jira access, which occurred between June 24th 9:55 AM UTC and 11:08 AM UTC due to a service scaling problem, has been resolved, and the incident is now closed.
Excerpts are shortened. Read the full incident on Jira's status page.
Attachment Loading Issue in C2C and Sandbox Migrations
-
resolved
We have resolved an issue that affected attachment loading during C2C and Sandbox data copy migrations from 19-06-2025 18:00 UTC to 24-06-2025 08:49 UTC. If you encountered this issue, please delete the affected projects from the destination site and re-run the migration. For...
Excerpts are shortened. Read the full incident on Jira's status page.
Users experiencing 'file failed to upload' errors when attempting to upload attachments in work items
-
resolved
Our team has now confirmed that attachment uploads are functioning as expected and that this issue is now resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Child work item panel is not loading intermitently
-
resolved
Between 2:12 UTC to 08:45 UTC, we experienced child work item panel not loading intermittently for Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Jira, JWM and JSM Email Automations delays for some users
-
resolved
The issues causing delayed emails from Jira have been resolved, and services are functioning normally for all affected users.
Excerpts are shortened. Read the full incident on Jira's status page.
Jira search impacted by timeouts
-
resolved
The team have validated the fix has resolved the issue.
Excerpts are shortened. Read the full incident on Jira's status page.
Some Third Party Apps Unresponsive
-
resolved
The Heroku team has now provided an update that this issue should now be resolved. For any further issues relating to this issue please continue to monitor the updates that are being provided by Heroku on their status page here: https://status.heroku.com/incidents/2822
Excerpts are shortened. Read the full incident on Jira's status page.
Forge invocation errors impacting some instances in Singapore region
-
resolved
Between 21:39 UTC on June 09, 2025 and 21:35 UTC on June 10, 2025, we experienced a forge invocation errors impacting a subset of market place apps for some Confluence, Jira Service Management, and Jira, and Atlassian Developer Cloud customers in the Singapore region. The issue...
Excerpts are shortened. Read the full incident on Jira's status page.
Customers may experience delays receiving emails
-
resolved
Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the...
Excerpts are shortened. Read the full incident on Jira's status page.
Administration is unreachable
-
resolved
The issue with the Administration accessibility has now been resolved, and the service is operating normally for all affected customers.
Excerpts are shortened. Read the full incident on Jira's status page.
Issues with authentication across multiple services
-
resolved
Monitoring has indicated that users are no longer receiving the error messages caused by this issue and it should now be fully resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
All Jira products experiencing degradations
-
resolved
Deployment of the fix for this issue has now completed rolling out and this should be resolved for all users.
Excerpts are shortened. Read the full incident on Jira's status page.
Users cannot create/update issues in Jira and JSM via Outlook
-
resolved
The problematic change that caused this issue has now been rolled back and service has now been restored.
Excerpts are shortened. Read the full incident on Jira's status page.
Issues with data pipelines for customers using GitHub for Jira Connector.
Names an upstream provider: GitHub.
-
resolved
Existing events are continuing to be processed. Any updates to existing entities such as pull requests will also correct and update the data here as required. If there are any concerns about impact to your site with this connector please reach out to support and the team will...
Excerpts are shortened. Read the full incident on Jira's status page.
Confluence, JIRA and JSM unavailability or degraded experience for some EU users
-
resolved
Between 7:37 and 8:06 UTC, Confluence, Jira, and JSM were unavailable or experienced degraded performance for some users in the European region. The issue has now been resolved, and the services are operating normally for all impacted customers.
Excerpts are shortened. Read the full incident on Jira's status page.
Management of Apps is partially unavailable on different platforms
-
resolved
Between 10:55 AM UTC to 13:15 PM UTC on April 28, 2025, we experienced partial unavailability in managing Forge apps; Such as lifecycle developer console usage, and the creation and deployment of Forge apps for Atlassian Partners, Jira Work Management, Jira, Atlassian Developer,...
Excerpts are shortened. Read the full incident on Jira's status page.
Automation Rule execution is delayed
-
resolved
Between 13:00 UTC to 23:00 UTC on April 23, 2025, we experienced automation rule execution delays for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally. For some high...
Excerpts are shortened. Read the full incident on Jira's status page.
Jira Software sprint field not visible
-
resolved
Between 02:00 UTC to 16:30 UTC April 18, 2025, the sprint field was not visible in issue view and Issue Search / filters were showing empty for the sprint field cell for some Jira customers. The empty sprint field cell issue was mitigated and appearing normally at 08:30 UTC and...
Excerpts are shortened. Read the full incident on Jira's status page.
Users experiencing issues loading some Dashboard widgets in Jira
-
resolved
Between 3:30 UTC to 23:00 UTC April 16, 2025, we experienced an issue with loading certain Jira Dashboard widgets for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Error loading objects for Assets in JSM and Jira for some regions
-
resolved
Our team has identified the issue causing problems with Assets loading within JSM and Jira and applied a fix. Assets are now functioning as expected across our products.
Excerpts are shortened. Read the full incident on Jira's status page.
Issues loading Administration across Atlassian Products
-
resolved
Between 00:00 UTC to 01:05 UTC 14 April, users attempting to load the Administration page for Atlassian products. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Issues accessing Jira and Confluence in some regions
-
resolved
We identified a temporary access issue affecting some customers using several Atlassian Cloud products. All affected products are now back online, and no further impacts have been observed. We apologize for any inconvenience this may have caused.
Excerpts are shortened. Read the full incident on Jira's status page.
Some customers are experiencing an issue viewing Team field in Jira issue view
-
resolved
Between March 21, 2025 17:00 UTC and March 24, 2025 17:39 UTC, some customers were not able to view and assign the team field value from the issue view in Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
New navigation experience incorrectly being displayed to some users in Jira
-
resolved
The issue with users seeing a different navigation experience should now be resolved. Any users that are unexpectedly still seeing this experience can refresh their browser window or navigate to any other page to restore the previous functionality.
Excerpts are shortened. Read the full incident on Jira's status page.
Some customers are experiencing an issue viewing Team field in Jira
-
resolved
On 20 March 2025, between 14:18 UTC and 22:43 UTC, some customers were not able to use the Team field to search and assign teams in Jira Work Management, Jira Service Management, and Jira. The issue has been resolved, and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Performance degradation for Jira and Confluence User
-
resolved
Between 14:36 UTC to 16:15 UTC, we experienced performance degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Users Encountering a Site Maintenance Message on APAC-Based Jira Sites
-
resolved
Between 07:45 UTC to 18:45 UTC, a very small number of customers for Confluence, Jira Work Management, Jira Service Management, and Jira in the APAC region experienced a site maintenance issue. The issue has now been resolved and the service is operating normally for all...
Excerpts are shortened. Read the full incident on Jira's status page.
Users may experience performance degradation when loading the issue view
-
resolved
Between 14:22 UTC to 16:41 UTC, we experienced performance degradation for Jira Service Management and Jira. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Automation rule execution are delayed
-
resolved
Between 13:00 UTC to 16:30 UTC, we experienced delays in automation processing across Confluence, Jira Service Management, and Jira, which was causing rules to appear stuck. The issue has been resolved and we expect new automations to continue processing without delay. For...
Excerpts are shortened. Read the full incident on Jira's status page.
Forge app installations failing at an increased rate
-
resolved
Between 05:30 UTC and 10:00 UTC, we experienced increased rates of Forge app installation, upgrade and uninstallation for Confluence and Jira. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Service Slowness in Multiple Products
-
resolved
Between 09:43 UTC to 15:55 UTC, we experienced delays in automation processing across Confluence, Jira Service Management, and Jira, which was causing rules to appear stuck. The issue has been resolved and we expect new automations to continue processing without delay. For...
Excerpts are shortened. Read the full incident on Jira's status page.
Some users are experiencing errors while creating new Jira and Confluence sites
-
resolved
On March 14th, 2025, between 09:00 and 19:14 UTC, some customers experienced issues creating new sites. The errors occurring for some users during new site creation should now be resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Degraded performance detected in Jira, Jira Work Management and Jira Service Management Issue View experience
-
resolved
A mitigation for the performance issues has been implemented and this incident is now resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Jira Platform Connection Errors
-
resolved
Our team has been monitoring this issue and can confirm that the errors that were previously occurring have now been resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Intermittent issue loading Jira reports for some users
-
resolved
Issues related to loading Jira reports should now be resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Issues with 403 user authentication errors across Atlassian products
-
resolved
We are aware of an issue that was impacting user authentication to Atlassian services between 6:10AM Tuesday 4th March UTC and 6:35AM Tuesday 4th March UTC. Users that were already logged in would not have been impacted by this issue. A deployment suspected of causing this issue...
Excerpts are shortened. Read the full incident on Jira's status page.
Forge distrubution tab doesn't work for some Forge applications
-
resolved
We confirmed incident has been resolved
Excerpts are shortened. Read the full incident on Jira's status page.
403 Errors experienced by iOS users when IP Allowlist and Mobile App policy with Allow access from any IP address are enabled
-
resolved
We are pleased to inform you that a new version of our app is now available on the Apple App Store. Please update your app to the latest version to resolve the issue.
Excerpts are shortened. Read the full incident on Jira's status page.
Email processing failing for Jira/Jira Service Management
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Jira and Confluence has degraded performance - scoped to Brazil only
-
resolved
Between February 10, 2025, at 17:04 UTC and 18:32 UTC, some customers for Jira Work Management, Jira Service Management, Jira, Jira Product Discovery Cloud and Confluence experienced degraded performance and 500 errors. We found that cloud products in Brazil encountered an...
Excerpts are shortened. Read the full incident on Jira's status page.
Jira is slow or inaccessible for some users
-
resolved
Between 05/Feb/25 2:30 PM UTC and 05/Feb/25 3:28 PM UTC some customers for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud experienced intermittent errors. We have identified the root cause of the intermittent errors and have mitigated the...
Excerpts are shortened. Read the full incident on Jira's status page.
Jira is slow or inaccessible for some users
-
resolved
All affected products are now back online and no further impact has been observed.
Excerpts are shortened. Read the full incident on Jira's status page.
Service access disruptions
-
resolved
All affected products are now back online and no further impact has been observed.
Excerpts are shortened. Read the full incident on Jira's status page.
Jira services are unavailable and have degraded performance in certain regions
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Issue with Adding Jira Products to Existing Sites
-
resolved
Between 12:30:00 UTC on 23/Jan/25 to 14:30:00 UTC on 23/Jan/25, we experienced a problem Issue with Adding Jira Products to Existing Sites. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Issues linking Confluence spaces to Jira Project
-
resolved
We have deployed a fix to resolve the issue. We discovered this also impacts linking Designs to Jira issues and this issue is now resolved as well.
Excerpts are shortened. Read the full incident on Jira's status page.
Issues linking Confluence spaces to Jira Project
-
resolved
Between 22/01 23:58 UTC to 23/01 01:18 UTC, we experienced issues linking Confluence Cloud spaces to Jira Cloud projects. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Intermittent login failures for Jira, Confluence and JSM customers
-
resolved
Between 13 Jan, 11:45 PM UTC to 14 Jan 07:10 AM UTC, we experienced intermittent login failures for Confluence, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Automation drop-down menu not rendering correctly
-
resolved
Between 10:00pm UTC on 09/Jan/25 to 3:00am UTC on 10/Jan/25, the Automation drop down menu for Jira Service Management and Jira was not rendering correctly. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Component field value not available
-
resolved
Between 11:30:00 UTC on 9/Jan/25 to 2:30:00 UTC on 10/Jan/25, we experienced a problem displaying the component values in Jira, Jira Work Management and Jira Service Management for some customers. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Smart values not replaced in Automation rules with Send web request action
-
resolved
Between 11:28:00 UTC on 22/Dec/24 to 16:41:00 UTC on 23/Dec/24, we experienced a problem when running Automation rules for Confluence, Jira Service Management, and Jira that prevented rules that contained a Send Web Request action with Smart Values from completing successfully....
Excerpts are shortened. Read the full incident on Jira's status page.
Advanced Roadmaps displaying Something went wrong
-
resolved
Between 02:04 UTC to 03:24 UTC, we experienced some failures in Advanced Roadmaps for Jiras where plans that displayed issues with newly created priorities were failing for Jira. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Unified EPIC colors (Purple) on boards
-
resolved
We experienced an issue where EPIC tickets appeared with a unified color on Jira boards. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Jira issues are not loading
-
resolved
Between 19-Dec 00:30 UTC - 06:22 UTC, some users can't load Jira issue view (full issue view) pages. This has now been fixed and services are now operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Editor on description field and comment are not working
-
resolved
Between 19-Dec 03:38 UTC and 05:38 UTC, some customers were unable to edit or see the description for specific issue type bug. The editor wasn't visible when trying to add new comments. This has now been mitigated and we've seen recovery. Services are now back to normal...
Excerpts are shortened. Read the full incident on Jira's status page.
Issues with attachments, including viewing previews, downloading and uploading
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
View Remaining XX comments is missing and users are not able to load more comments.
-
resolved
Between 08:30 UTC and 22:19 UTC, we experienced an issue that caused "View Remaining XX comments" not to load for Jira Service Management and Jira. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Errors on AI features
-
resolved
Between 3:16pm PST and 7:38pm PST, we experienced an outage for Rovo and all AI features across Atlassian Products. The issue has been resolved and the service is operating normally
Excerpts are shortened. Read the full incident on Jira's status page.
AI features degraded
-
resolved
Between 12:13 AM UTC to 01:30 AM UTC, we experienced a degraded experience for AI features in Confluence, Jira Service Management, Jira, and Rovo. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Jira Loading slow / Inaccessible with 5XX errors
-
resolved
Between 09:00 UTC and 09:51 UTC, we experienced degraded performance for some Jira Service Management and Jira customers. The issue has been resolved, and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Automation match() smart value with regex is not working
-
resolved
Between 24/11/2024 09:46 PM UTC to 27/11/2024 5:58PM UTC, we experienced an issue where Automation match() smart values with regex are not working as expected for Confluence, Jira Service Management, and Jira. This issue has now been resolved, and automation rules are...
Excerpts are shortened. Read the full incident on Jira's status page.
Microsoft API Failure Impacting Jira and JSM Email Processing
-
resolved
We are pleased to inform you that the recent issues affecting email processing for Microsoft accounts, which impacted our Jira and JSM Cloud customers, have been successfully resolved. This resolution follows Microsoft’s reversion of the changes that initially caused the...
Excerpts are shortened. Read the full incident on Jira's status page.
previews are not available in some cases
-
resolved
Between 07:50 UTC to 11:31 UTC, some customers experienced previews of attachments unavailable for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. We have deployed a fix to mitigate the issue and have verified that the services have...
Excerpts are shortened. Read the full incident on Jira's status page.
Epic panel items don’t load or have performance problems.
-
resolved
We have identified the root cause of the recent issue affecting Epic panels not loading and have successfully applied a fix. The issue is now resolved.
Excerpts are shortened. Read the full incident on Jira's status page.
Jira migrations including AR plans are getting stuck on JCMA 1.12.10
-
resolved
The issues affecting certain tenants have been successfully resolved, and the impact has been fully mitigated at this time.
Excerpts are shortened. Read the full incident on Jira's status page.
Automation logs are not accessible and delayed
-
resolved
Between 06/Nov/24 12:00 AM UTC to 06/Nov/24 9:22 AM UTC, we experienced Automation Audit Logs not loading for customers intermittently for Confluence, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Unified EPIC colors on Jira Software Board and timeline
-
resolved
Between 08:00 UTC to 23:00 UTC, we experienced an issue where all epic colours are displaying as purple in timelines and boards for some customer. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Automation limits are incorrect for some Cloud customers
-
resolved
Between 04/Nov/24 11:30 PM UTC to 05/Nov/24 10:47 AM UTC, we experienced problems with the automation limits for some Cloud customers for Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Jira dashboards and gadgets not loading
-
resolved
Between 05:00 UTC to 11:20 UTC, we experienced problems with dashboards and gadgets not loading for Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Jira responding with 500 error for some Jira customers
-
resolved
Between 08:30 - 12:00 UTC, we experienced 500 errors for Jira Work Management, Jira Service Management, and Jira for some customers. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.
Unable to invite new users due to missing recaptcha token
-
resolved
Between 08:00 UTC to 11:54 UTC, we experienced problems with the invitation of new users for Cloud customers on admin.atlassian.com. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Jira's status page.