Jira Status

Resolved: The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Monitoring: We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users.

After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal.

We apologize for any inconvenience this may have caused.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

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.

Monitoring: Impact

Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities.

Current Status

We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident.

Next Steps

Further updates will be communicated in 60 minutes.

Investigating: We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

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.

Identified: The incident involves Ecosystem and Jira products, specifically affecting the Forge Jira Custom Fields. Customers may experience a loss of values upon selection on the Issue Create Screen.

The root cause is identified and we are working on deploying a fix.

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.

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.

Investigating: Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

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

Resolved: The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Monitoring: We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users.

After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal.

We apologize for any inconvenience this may have caused.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

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.

Monitoring: Impact

Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities.

Current Status

We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident.

Next Steps

Further updates will be communicated in 60 minutes.

Investigating: We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

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.

Identified: We understand that Users are experiencing issues with Forge Custom Fields not retaining selected values on Issue Create Screen. We have identified the root cause and actively working on deploying a fix. Issue start time: 2025-11-20T07:00

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.

Identified: The incident involves Ecosystem and Jira products, specifically affecting the Forge Jira Custom Fields. Customers may experience a loss of values upon selection on the Issue Create Screen.

The root cause is identified and we are working on deploying a fix.

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.

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.

Investigating: Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

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

Resolved: The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Monitoring: We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users.

After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal.

We apologize for any inconvenience this may have caused.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

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.

Monitoring: Impact

Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities.

Current Status

We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident.

Next Steps

Further updates will be communicated in 60 minutes.

Investigating: We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

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.

Identified: The incident involves Ecosystem and Jira products, specifically affecting the Forge Jira Custom Fields. Customers may experience a loss of values upon selection on the Issue Create Screen.

The root cause is identified and we are working on deploying a fix.

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.

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.

Investigating: Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

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

Resolved: The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Monitoring: We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users.

After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal.

We apologize for any inconvenience this may have caused.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

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.

Monitoring: Impact

Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities.

Current Status

We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident.

Next Steps

Further updates will be communicated in 60 minutes.

Investigating: We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

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.

Identified: The incident involves Ecosystem and Jira products, specifically affecting the Forge Jira Custom Fields. Customers may experience a loss of values upon selection on the Issue Create Screen.

The root cause is identified and we are working on deploying a fix.

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.

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.

Investigating: Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

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

Resolved: The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Monitoring: We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users.

After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal.

We apologize for any inconvenience this may have caused.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

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.

Monitoring: Impact

Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities.

Current Status

We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident.

Next Steps

Further updates will be communicated in 60 minutes.

Investigating: We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

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.

Identified: The incident involves Ecosystem and Jira products, specifically affecting the Forge Jira Custom Fields. Customers may experience a loss of values upon selection on the Issue Create Screen.

The root cause is identified and we are working on deploying a fix.

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.

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.

Investigating: Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

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

Resolved: The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Monitoring: We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users.

After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal.

We apologize for any inconvenience this may have caused.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

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.

Monitoring: Impact

Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities.

Current Status

We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident.

Next Steps

Further updates will be communicated in 60 minutes.

Investigating: We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

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.

Identified: The incident involves Ecosystem and Jira products, specifically affecting the Forge Jira Custom Fields. Customers may experience a loss of values upon selection on the Issue Create Screen.

The root cause is identified and we are working on deploying a fix.

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.

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.

Investigating: Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

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

Resolved: The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Monitoring: We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users.

After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal.

We apologize for any inconvenience this may have caused.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

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.

Monitoring: Impact

Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities.

Current Status

We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident.

Next Steps

Further updates will be communicated in 60 minutes.

Investigating: We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

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.

Identified: The incident involves Ecosystem and Jira products, specifically affecting the Forge Jira Custom Fields. Customers may experience a loss of values upon selection on the Issue Create Screen.

The root cause is identified and we are working on deploying a fix.

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.

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.

Investigating: Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

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

Resolved: The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Monitoring: We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users.

After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal.

We apologize for any inconvenience this may have caused.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

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.

Monitoring: Impact

Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities.

Current Status

We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident.

Next Steps

Further updates will be communicated in 60 minutes.

Investigating: We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

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.

Identified: The incident involves Ecosystem and Jira products, specifically affecting the Forge Jira Custom Fields. Customers may experience a loss of values upon selection on the Issue Create Screen.

The root cause is identified and we are working on deploying a fix.

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.

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.

Investigating: Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

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

Resolved: The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Monitoring: We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users.

After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal.

We apologize for any inconvenience this may have caused.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

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.

Monitoring: Impact

Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities.

Current Status

We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident.

Next Steps

Further updates will be communicated in 60 minutes.

Investigating: We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

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.

Identified: The incident involves Ecosystem and Jira products, specifically affecting the Forge Jira Custom Fields. Customers may experience a loss of values upon selection on the Issue Create Screen.

The root cause is identified and we are working on deploying a fix.

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.

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.

Investigating: Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

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

Resolved: The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Monitoring: We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users.

After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal.

We apologize for any inconvenience this may have caused.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

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.

Monitoring: Impact

Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities.

Current Status

We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident.

Next Steps

Further updates will be communicated in 60 minutes.

Investigating: We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

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.

Identified: The incident involves Ecosystem and Jira products, specifically affecting the Forge Jira Custom Fields. Customers may experience a loss of values upon selection on the Issue Create Screen.

The root cause is identified and we are working on deploying a fix.

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.

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.

Investigating: Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

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

Resolved: The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Monitoring: We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users.

After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal.

We apologize for any inconvenience this may have caused.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

Identified: We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

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.

Monitoring: Impact

Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities.

Current Status

We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident.

Next Steps

Further updates will be communicated in 60 minutes.

Investigating: We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

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.

Identified: The incident involves Ecosystem and Jira products, specifically affecting the Forge Jira Custom Fields. Customers may experience a loss of values upon selection on the Issue Create Screen.

The root cause is identified and we are working on deploying a fix.

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.

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.

Investigating: Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

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