Get email notifications whenever Jira Service Management creates, updates or resolves an incident.
Get text message notifications whenever Jira Service Management creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever Jira Service Management creates an incident, updates an incident, resolves an incident or changes a component status.
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
Past Incidents
Oct 29, 2025
No incidents reported today.
Oct 28, 2025
No incidents reported.
Oct 27, 2025
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 services have recovered. The root cause is still being investigated and will be provided in the post incident review. The conditions that cause the errors are being addressed and we're actively working on a permanent fix. The issue has been resolved and the services are operating normally.
Oct 27, 17:50 UTC
Oct 27, 17:50 UTC
Investigating -
Impact
Jira Software users are experiencing service degradation in viewIssue and createIssue. This issue affects multiple regions, with noticeable impacts on user functionalities across these experiences. This is potentially affecting Jira Service Management and Jira Work Management.
Next Steps - The team is investigating and further communications will be provided in 60 minutes.
Oct 27, 16:33 UTC
Jira Software users are experiencing service degradation in viewIssue and createIssue. This issue affects multiple regions, with noticeable impacts on user functionalities across these experiences. This is potentially affecting Jira Service Management and Jira Work Management.
Next Steps - The team is investigating and further communications will be provided in 60 minutes.
Oct 27, 16:33 UTC
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 restored.
Oct 27, 03:23 UTC
We disabled the feature that was causing this issue and normal services within Jira and Jira Service Management are now fully restored.
Oct 27, 03:23 UTC
Investigating -
We are aware that some customers using Jira Software or Jira Service Management are experiencing issues including 'something went wrong' errors with various functionalities such as viewing boards, issues, and creating issues.
Our team is investigating with urgency and we will provide an update within an hour.
Oct 27, 03:00 UTC
Our team is investigating with urgency and we will provide an update within an hour.
Oct 27, 03:00 UTC
Oct 26, 2025
No incidents reported.
Oct 25, 2025
No incidents reported.
Oct 24, 2025
No incidents reported.
Oct 23, 2025
No incidents reported.
Oct 22, 2025
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.
Oct 22, 06:47 UTC
This issue is marked as resolved.
Oct 22, 06:47 UTC
Oct 21, 2025
Postmortem -
Read details
Oct 24, 17:52 UTC
Oct 24, 17:52 UTC
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 inconvenience that this incident has caused and we will provide further information when the Post Incident Investigation has been completed.
Oct 21, 05:24 UTC
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 inconvenience that this incident has caused and we will provide further information when the Post Incident Investigation has been completed.
Oct 21, 05:24 UTC
Update -
The issue relating to the Atlassian Support portal displaying a message to customers to use our temporary support channel has now been resolved. The Atlassian Support portal is fully functional for any ongoing support issues.
With regards to other Atlassian products, we continue to see recovery continuing across all impacted products and our teams are continuing to monitor as the recovery continues.
We will provide further update on our recovery status within two hours.
Oct 21, 03:24 UTC
With regards to other Atlassian products, we continue to see recovery continuing across all impacted products and our teams are continuing to monitor as the recovery continues.
We will provide further update on our recovery status within two hours.
Oct 21, 03:24 UTC
Update -
We continue to see recovery progressing across all impacted products as backlogged items continue to be processed.
The Atlassian Support portal is currently displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message.
We will provide further update on our recovery status in two hours.
Oct 21, 01:07 UTC
The Atlassian Support portal is currently displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message.
We will provide further update on our recovery status in two hours.
Oct 21, 01:07 UTC
Update -
Our team is now seeing recovery across all impacted Atlassian products. We are continuing to monitor for individual products that may still be processing backlogged items now that services are restored.
The Atlassian Support portal is currently still displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message.
We will provide further update on our recovery status in one hour.
Oct 21, 00:03 UTC
The Atlassian Support portal is currently still displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message.
We will provide further update on our recovery status in one hour.
Oct 21, 00:03 UTC
Update -
Our teams are continuing to monitor the recovery of systems across Atlassian products. This update is to inform that the Atlassian Support portal is fully operational at this time for customers that wish to contact support.
Oct 20, 22:58 UTC
Oct 20, 22:58 UTC
Update -
Monitoring - We've started seeing continued product experience improvement.
While we still have a backlog of event processing, we are seeing improvements in systems operational capabilities across all products. We estimate a significant improvement with the next few hours and will continue to monitor the health of AWS services and the effects on Atlassian customers. We appreciate your continued patience and remain committed to full resolution as we work through this situation. We will post our next update in two hours.
Oct 20, 21:26 UTC
While we still have a backlog of event processing, we are seeing improvements in systems operational capabilities across all products. We estimate a significant improvement with the next few hours and will continue to monitor the health of AWS services and the effects on Atlassian customers. We appreciate your continued patience and remain committed to full resolution as we work through this situation. We will post our next update in two hours.
Oct 20, 21:26 UTC
Monitoring -
There have been no changes since our last update. We will provide our next updated by 9:00PM UTC or sooner as new information becomes available.
We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation.
Oct 20, 18:38 UTC
We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation.
Oct 20, 18:38 UTC
Update -
We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.
Oct 20, 17:43 UTC
Oct 20, 17:43 UTC
Update -
Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.
Oct 20, 17:27 UTC
Oct 20, 17:27 UTC
Update -
Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and while we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will be providing hourly updates on this issue.
Oct 20, 16:36 UTC
Oct 20, 16:36 UTC
Update -
Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and while we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will be providing hourly updates on this issue.
Oct 20, 16:35 UTC
Oct 20, 16:35 UTC
Update -
Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.
Oct 20, 15:21 UTC
Oct 20, 15:21 UTC
Update -
Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.
Oct 20, 15:20 UTC
Oct 20, 15:20 UTC
Update -
We understand your pain and mitigating or fixing this issue is of utmost importance. Our public cloud provider is actively working to mitigate this issue on priority. We have been seeing partial operational success. We appreciate your patience and will continue to provide updates every hour or sooner.
Oct 20, 14:03 UTC
Oct 20, 14:03 UTC
Update -
Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.
Oct 20, 13:58 UTC
Oct 20, 13:58 UTC
Update -
Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.
Oct 20, 13:56 UTC
Oct 20, 13:56 UTC
Update -
Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.
Oct 20, 13:07 UTC
Oct 20, 13:07 UTC
Update -
Atlassian team is actively engaged and continues to work with our public cloud provider to mitigate this issue at the earliest. We are starting to see partial operations succeed. We appreciate your patience. We shall continue to share updates every hour, if not sooner.
Oct 20, 12:06 UTC
Oct 20, 12:06 UTC
Update -
We continue to work with our public cloud provider towards mitigating the issue at the earliest. We appreciate your patience. We shall continue to share updates every hour, if not sooner.
Oct 20, 11:08 UTC
Oct 20, 11:08 UTC
Identified -
We understand that our public cloud provider has identified the cause of the issue. We are starting to see some recovery and is working towards mitigation. We appreciate your patience.
We shall continue to share updates every hour, if not sooner.
Oct 20, 09:58 UTC
We shall continue to share updates every hour, if not sooner.
Oct 20, 09:58 UTC
Update -
We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment.
We shall continue to share updates every hour, if not sooner.
Oct 20, 09:24 UTC
We shall continue to share updates every hour, if not sooner.
Oct 20, 09:24 UTC
Update -
We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment.
We shall continue to share updates every hour, if not sooner.
Oct 20, 09:23 UTC
We shall continue to share updates every hour, if not sooner.
Oct 20, 09:23 UTC
Update -
Atlassian Cloud services are impacted and we are aware that our customers might not be able to create support tickets. Our teams are actively investigating the same.
We shall keep you informed of the progress every hour.
Oct 20, 08:24 UTC
We shall keep you informed of the progress every hour.
Oct 20, 08:24 UTC
Investigating -
We have noticed that Atlassian Cloud services are impacted and our teams are actively investigating the same.
We shall keep you informed of the progress every hour.
Oct 20, 07:56 UTC
We shall keep you informed of the progress every hour.
Oct 20, 07:56 UTC
Oct 20, 2025
Oct 19, 2025
No incidents reported.
Oct 18, 2025
No incidents reported.
Oct 17, 2025
No incidents reported.
Oct 16, 2025
No incidents reported.
Oct 15, 2025
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 Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Approximately 50 percent of Automation API calls were affected in the us-east-1 region with customers receiving 429 status codes.
Current Status
The incident has been mitigated by increasing the API Gateway rate limit service quota and disabling the internal service that was causing high traffic volume.
Next Steps
We are conducting a root cause analysis of the internal service. A post incident review will be conducted.
Oct 15, 16:16 UTC
Impact
Some customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Approximately 50 percent of Automation API calls were affected in the us-east-1 region with customers receiving 429 status codes.
Current Status
The incident has been mitigated by increasing the API Gateway rate limit service quota and disabling the internal service that was causing high traffic volume.
Next Steps
We are conducting a root cause analysis of the internal service. A post incident review will be conducted.
Oct 15, 16:16 UTC
Monitoring -
We have recovered from a issue which saw degraded Automation experience.
Impact
Some Customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running.
Current Status
The incident has been mitigated and we continue to investigate the cause of this incident
Next Steps
We are continuing to monitor the service, and will provide further updates in the next two hours
Oct 15, 15:26 UTC
Impact
Some Customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running.
Current Status
The incident has been mitigated and we continue to investigate the cause of this incident
Next Steps
We are continuing to monitor the service, and will provide further updates in the next two hours
Oct 15, 15:26 UTC
Update -
Atlassian team is actively investigating the issue with UI based Customer interactions.
Existing automation rules continue to run without any issue. Accessing automation rules and creating new automation rules could lead to intermittent failures.
We shall keep you informed of the progress in next 2 hours, if not sooner.
Oct 15, 14:34 UTC
Existing automation rules continue to run without any issue. Accessing automation rules and creating new automation rules could lead to intermittent failures.
We shall keep you informed of the progress in next 2 hours, if not sooner.
Oct 15, 14:34 UTC
Investigating -
UI based Customer interactions are currently degraded and our team is actively investigating the same. We shall keep you informed of the progress in next 2 hours.
Oct 15, 13:43 UTC
Oct 15, 13:43 UTC