All Systems Operational

About This Site

Here we will post updates about Jira's service availability. For status information about other Atlassian products or services, please visit the Atlassian status page.

Viewing content Operational
Create and edit Operational
Authentication and User Management Operational
Search Operational
Notifications Operational
Administration Operational
Marketplace Operational
Mobile Operational
Purchasing & Licensing Operational
Signup Operational
Automation for Jira Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
May 26, 2026

No incidents reported today.

May 25, 2026

No incidents reported.

May 24, 2026

No incidents reported.

May 23, 2026

No incidents reported.

May 22, 2026

No incidents reported.

May 21, 2026

No incidents reported.

May 20, 2026
Forge custom fields are not getting created
Resolved - The root cause has been identified and a fix has been applied.

Full service restoration has been completed.
May 20, 14:14 UTC
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 UTC
Update - 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 UTC
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, 09:17 UTC
May 19, 2026

No incidents reported.

May 18, 2026

No incidents reported.

May 17, 2026

No incidents reported.

May 16, 2026

No incidents reported.

May 15, 2026

No incidents reported.

May 14, 2026
Users experiencing issues accessing multiple Atlassian products
Postmortem - Read details
May 19, 19:04 UTC
Resolved - All products and services impacted by this incident should now be fully recovered, and this incident is resolved.
May 14, 06:48 UTC
Update - We are approaching full system recovery at this time, and are performing final confirmations that services are restored.
May 14, 06:41 UTC
Update - 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, 06:40 UTC
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, 05:43 UTC
Update - 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, 05:34 UTC
Update - 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, 05:24 UTC
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, 05:11 UTC
Update - 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, 05:03 UTC
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, 04:54 UTC
May 13, 2026
Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some users
Resolved - We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.
May 13, 09:59 UTC
Update - 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, 08:42 UTC
Update - 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, 07:42 UTC
Update - 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, 06:38 UTC
Update - 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, 05:38 UTC
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, 02:41 UTC
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, 01:37 UTC
May 12, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage