Atlassian (Jira) Outage History
Uptime record, past incidents, and downtime history for Atlassian (Jira).
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 76% | 25 | 6 |
| April 2026 | 86.7% | 30 | 4 |
| March 2026 | 90.3% | 31 | 3 |
| February 2026 | 100% | 5 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Feb 24
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
Forge custom fields are not getting created
Started: May 20, 9:17 AM
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, however existing deployments with custom fields are running without any issues.
May 20, 12:06 PM
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.
May 20, 11:20 AM
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.
May 20, 9:17 AM
Users experiencing issues accessing multiple Atlassian products
Started: May 14, 4:54 AM
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 validated and the incident is closed.
May 14, 6:41 AM
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 validated and the incident is closed.
May 14, 6:40 AM
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 place.
May 14, 5:43 AM
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 within an hour as we are able to progress mitigating this issue.
May 14, 5:34 AM
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 continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.
We will provide further update within one hour, or sooner as further information becomes available.
May 14, 5:24 AM
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.
May 14, 5:11 AM
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 available.
May 14, 5:03 AM
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 details within the next hour or sooner if further information becomes available
May 14, 4:54 AM
Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some users
Started: May 13, 1:37 AM
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.
May 13, 8:42 AM
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.
May 13, 7:42 AM
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.
May 13, 6:38 AM
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 within one hour or sooner if available.
May 13, 5:38 AM
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 information is available prior to that time.
May 13, 2:41 AM
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.
May 13, 1:37 AM
Multiple Atlassian services are experiencing issues
Started: May 8, 1:31 AM
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 apologise for the disruption and thank you for your patience.
May 8, 11:12 AM
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.
May 8, 8:03 AM
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 triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.
May 8, 5:53 AM
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 product page.
May 8, 4:10 AM
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.
May 8, 4:10 AM
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.
May 8, 4:10 AM
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.
May 8, 3:00 AM
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.
May 8, 3:00 AM
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.
May 8, 2:15 AM
investigating
We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.
May 8, 1:31 AM
Jira users unable to log time while on business board
Started: May 6, 3:18 AM
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.
May 6, 4:16 AM
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.
May 6, 3:18 AM
The Work Item view experience of Jira is degraded
Started: May 2, 12:55 AM
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.
May 2, 2:00 AM
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.
May 2, 1:38 AM
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.
May 2, 12:55 AM
April 2026
Delays in Jira webhook delivery
Started: Apr 30, 8:59 AM
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.
Apr 30, 1:36 PM
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.
Apr 30, 10:05 AM
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.
Apr 30, 8:59 AM
Disrupted Rovo availability for Automation rules
Started: Apr 14, 12:12 PM
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.
Apr 14, 3:46 PM
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.
Apr 14, 2:11 PM
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.
Apr 14, 12:25 PM
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 information becomes available.
Apr 14, 12:12 PM
Users experiencing issues with login across Atlassian products
Started: Apr 13, 7:29 AM
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.
Apr 13, 8:33 AM
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 will provide an update within 1 hour.
Apr 13, 7:29 AM
Multiple products impacted by search failures
Started: Apr 8, 5:41 AM
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.
Apr 8, 9:03 AM
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 resolution.
We will provide further update within 1 hour.
Apr 8, 9:03 AM
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 this page as performance fully recovers.
Apr 8, 8:33 AM
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 resolution.
We will provide further update within 1 hour.
Apr 8, 8:33 AM
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.
Apr 8, 7:40 AM
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 resolution.
We will provide further update within 1 hour.
Apr 8, 7:40 AM
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 resolution.
We will provide further update within 1 hour.
Apr 8, 6:25 AM
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.
Apr 8, 6:25 AM
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.
Apr 8, 6:24 AM
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 update within 1 hour.
Apr 8, 6:01 AM
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.
Apr 8, 6:01 AM
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.
Apr 8, 5:41 AM
March 2026
Automations aren't triggering on work item creation, field updates, or comment additions
Started: Mar 18, 11:29 AM
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.
Mar 18, 11:44 PM
monitoring
We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.
Mar 18, 9:44 PM
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.
Mar 18, 2:53 PM
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.
Mar 18, 2:03 PM
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.
Mar 18, 2:01 PM
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.
Mar 18, 1:07 PM
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 information is available.
Mar 18, 12:24 PM
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.
Mar 18, 11:32 AM
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.
Mar 18, 11:29 AM