Jira Service Management Status

Resolved: The team has verified that the fix has successfully propagated to all accounts. Impacted customers will receive an email follow-up containing additional information.

Monitoring: The team has corrected entitlements for impacted customers and reverted plans to Service Collection Free.

We are now monitoring the rollout to confirm the fix has successfully propagated to all accounts.

Identified: Our team has identified the steps required to restore the affected sites and is actively working to restore original entitlements.

We will provide our next update in four hours, or sooner if we have meaningful progress to share.

Identified: Our team continues active testing of the fix to restore customer accounts affected by this incident.

We will provide further update within two hours or sooner.

Identified: Our team is now actively testing the fix required to properly restore customer accounts impacted by this incident.

We will provide further update within two hours to provide guidance on our expected timeline for the resolution to be fully completed.

Identified: During an update designed to enable Service Collection for our Jira Service Management Free customers, some of these customers were incorrectly updated to a Standard Service Collection no-cost trial, and received a notification that they would now need to pay for this service at the end of their trial period.

Please rest assured that requiring payment was not an intended change for these Free customers, and we are working to restore these accounts back to their Free status.

We will provide further update within two hours or earlier if there is important information to share.

Investigating: We are aware of reports that Free JSM customers received emails stating that their plans have been adjusted to Standard Trial Service Collection accounts.

Our team is working urgently to address this issue and we plan to revert the change for all customers that are impacted, to reinstate their Free plan status.

Please note that if your plan has been incorrectly updated, you will be placed into a no-cost trial status.

There is currently no action required from those customers that have incorrectly received these emails.

We will provide further update within an hour as our effort continues.

Resolved: On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Identified: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

Identified: Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

Identified: Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Identified: Impact

The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.

Current Status

Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.

Next Steps

The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Resolved: On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Identified: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

Identified: Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

Identified: Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Identified: Impact

The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.

Current Status

Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.

Next Steps

The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Resolved: On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Identified: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

Identified: Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

Identified: Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Identified: Impact

The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.

Current Status

Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.

Next Steps

The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Resolved: On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Identified: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

Identified: Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

Identified: Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Identified: Impact

The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.

Current Status

Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.

Next Steps

The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Resolved: On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Identified: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

Identified: Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

Identified: Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Identified: Impact

The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.

Current Status

Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.

Next Steps

The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Resolved: On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Identified: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

Identified: Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

Identified: Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Identified: Impact

The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.

Current Status

Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.

Next Steps

The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Resolved: On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Identified: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

Identified: Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

Identified: Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Identified: Impact

The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.

Current Status

Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.

Next Steps

The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Resolved: On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Identified: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

Identified: Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

Identified: Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Identified: Impact

The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.

Current Status

Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.

Next Steps

The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Resolved: On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Identified: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

Identified: Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

Identified: Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Identified: Impact

The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.

Current Status

Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.

Next Steps

The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Resolved: On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Identified: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

Identified: Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

Identified: Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Identified: Impact

The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.

Current Status

Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.

Next Steps

The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Resolved: On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Identified: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

Identified: Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

Identified: Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Identified: Impact

The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.

Current Status

Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.

Next Steps

The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Resolved: On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

Identified: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

Identified: Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

Identified: Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.

Identified: Impact

The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.

Current Status

Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.

Next Steps

The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

Identified: We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.

We will continue to share additional updates here as more information is available.