Jira Status

Resolved: Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Resolved: On February 5, 2026, JIRA and JIRA Service Management 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.

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

Identified: Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.

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

Identified: We have identified the 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: Some users in the us-east-1 region cannot access Jira and JSM.

We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.

We will provide update on the progress in next 60 minutes or sooner.

Investigating: Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same.

We will provide update on the progress in next 60 minutes or sooner.

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: Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Resolved: On February 5, 2026, JIRA and JIRA Service Management 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.

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

Identified: Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.

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

Identified: We have identified the 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: Some users in the us-east-1 region cannot access Jira and JSM.

We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.

We will provide update on the progress in next 60 minutes or sooner.

Investigating: Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same.

We will provide update on the progress in next 60 minutes or sooner.

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: Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Resolved: On February 5, 2026, JIRA and JIRA Service Management 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.

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

Identified: Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.

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

Identified: We have identified the 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: Some users in the us-east-1 region cannot access Jira and JSM.

We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.

We will provide update on the progress in next 60 minutes or sooner.

Investigating: Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same.

We will provide update on the progress in next 60 minutes or sooner.

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: Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Resolved: On February 5, 2026, JIRA and JIRA Service Management 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.

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

Identified: Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.

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

Identified: We have identified the 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: Some users in the us-east-1 region cannot access Jira and JSM.

We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.

We will provide update on the progress in next 60 minutes or sooner.

Investigating: Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same.

We will provide update on the progress in next 60 minutes or sooner.

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: Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Resolved: On February 5, 2026, JIRA and JIRA Service Management 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.

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

Identified: Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.

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

Identified: We have identified the 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: Some users in the us-east-1 region cannot access Jira and JSM.

We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.

We will provide update on the progress in next 60 minutes or sooner.

Investigating: Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same.

We will provide update on the progress in next 60 minutes or sooner.

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: Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Resolved: On February 5, 2026, JIRA and JIRA Service Management 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.

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

Identified: Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.

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

Identified: We have identified the 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: Some users in the us-east-1 region cannot access Jira and JSM.

We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.

We will provide update on the progress in next 60 minutes or sooner.

Investigating: Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same.

We will provide update on the progress in next 60 minutes or sooner.

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: Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Resolved: On February 5, 2026, JIRA and JIRA Service Management 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.

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

Identified: Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.

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

Identified: We have identified the 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: Some users in the us-east-1 region cannot access Jira and JSM.

We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.

We will provide update on the progress in next 60 minutes or sooner.

Investigating: Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same.

We will provide update on the progress in next 60 minutes or sooner.

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: Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Resolved: On February 5, 2026, JIRA and JIRA Service Management 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.

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

Identified: Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.

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

Identified: We have identified the 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: Some users in the us-east-1 region cannot access Jira and JSM.

We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.

We will provide update on the progress in next 60 minutes or sooner.

Investigating: Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same.

We will provide update on the progress in next 60 minutes or sooner.

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: Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Resolved: On February 5, 2026, JIRA and JIRA Service Management 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.

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

Identified: Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.

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

Identified: We have identified the 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: Some users in the us-east-1 region cannot access Jira and JSM.

We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.

We will provide update on the progress in next 60 minutes or sooner.

Investigating: Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same.

We will provide update on the progress in next 60 minutes or sooner.

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: Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Resolved: On February 5, 2026, JIRA and JIRA Service Management 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.

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

Identified: Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.

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

Identified: We have identified the 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: Some users in the us-east-1 region cannot access Jira and JSM.

We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.

We will provide update on the progress in next 60 minutes or sooner.

Investigating: Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same.

We will provide update on the progress in next 60 minutes or sooner.

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: Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Investigating: Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

Resolved: On February 5, 2026, JIRA and JIRA Service Management 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.

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

Identified: Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.

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

Identified: We have identified the 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: Some users in the us-east-1 region cannot access Jira and JSM.

We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.

We will provide update on the progress in next 60 minutes or sooner.

Investigating: Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same.

We will provide update on the progress in next 60 minutes or sooner.

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.