All Systems Operational

About This Site

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

Jira Service Management Web Operational
Service Portal Operational
Opsgenie Incident Flow Operational
Opsgenie Alert Flow Operational
Opsgenie Incident Flow Operational
Opsgenie Alert Flow Operational
Jira Service Management Email Requests Operational
Authentication and User Management Operational
Purchasing & Licensing Operational
Signup Operational
Automation for Jira Operational
Assist Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Jan 7, 2026
Disrupted Automation for Jira triggers not running for some customers
Resolved - Rerunning the remaining Automation for Jira rules that failed for affected customers is complete.
This update resolves the issue.
Jan 7, 11:32 UTC
Update - 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 rerunning the remaining Automation for Jira rules that failed earlier.

We will provide the next update once replaying the historical events is complete.
Jan 7, 08:37 UTC
Update - 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 the next update in about two hours or sooner.
Jan 7, 04:43 UTC
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.

During Asia Pacific hours tomorrow, the team plans to replay historical events.
Team will continue monitoring. Next update will tomorrow.
Jan 6, 14:04 UTC
Update - 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 has been identified, and the team is actively working on restoring the operations back to normal as soon as possible.

Workaround to manage critical rules, disable and re-enable each automation rule. This triggers the rule and must be done for every critical rule.

We will provide the next update in about two hours or sooner.
Jan 6, 12:19 UTC
Update - 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 the cause and we continue working on restoring the operations back to normal as soon as possible.

In the meantime, workaround to manage business critical rules is to disable and then re-enable each automation rule. This action triggers the rule and must be done for every critical rule.

We will provide the next update in about two hours or sooner.
Jan 6, 10:11 UTC
Update - 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.
Jan 6, 07:58 UTC
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.
Jan 6, 06:17 UTC
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 within 60 minutes.
Jan 6, 05:18 UTC
Jan 6, 2026
Jan 5, 2026

No incidents reported.

Jan 4, 2026

No incidents reported.

Jan 3, 2026

No incidents reported.

Jan 2, 2026

No incidents reported.

Jan 1, 2026

No incidents reported.

Dec 31, 2025

No incidents reported.

Dec 30, 2025

No incidents reported.

Dec 29, 2025

No incidents reported.

Dec 28, 2025

No incidents reported.

Dec 27, 2025
Outbound Email, Mobile Push Notifications, and Support Ticket Delivery Impacting All Cloud Products
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.
Dec 27, 05:20 UTC
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 progress.
Dec 27, 04:42 UTC
Update - We are actively investigating this issue and will share additional updates as soon as more information becomes available.
We sincerely apologize for the inconvenience this has caused.
Dec 27, 03:28 UTC
Investigating - We have identified an issue with outbound email delivery and mobile push notifications that is impacting Atlassian Cloud customers across all products.
Importantly, customer support tickets are unable to be generated during this time. We apologise for any inconvenience this may cause.
We are currently investigating and will provide more information as it becomes available.
Dec 27, 02:48 UTC
Dec 26, 2025

No incidents reported.

Dec 25, 2025

No incidents reported.

Dec 24, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage