Jira Status

Resolved: On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.

Monitoring: We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

Monitoring: The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

Identified: We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Investigating: We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Resolved: We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

Identified: Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

Identified: While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident.

We will provide an update on the progress within one hour.

Identified: Our team has been able to confirm that new automation events should now be processed correctly.

We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

Identified: The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

Identified: Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

Investigating: At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

Resolved: All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

Identified: Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.

Identified: It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.

Identified: Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

Investigating: We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Investigating: We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available

Resolved: On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.

Monitoring: We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

Monitoring: The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

Identified: We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Investigating: We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Resolved: We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

Identified: Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

Identified: While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident.

We will provide an update on the progress within one hour.

Identified: Our team has been able to confirm that new automation events should now be processed correctly.

We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

Identified: The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

Identified: Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

Investigating: At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

Resolved: All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

Identified: Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.

Identified: It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.

Identified: Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

Investigating: We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Investigating: We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available

Resolved: On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.

Monitoring: We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

Monitoring: The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

Identified: We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Investigating: We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Resolved: We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

Identified: Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

Identified: While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident.

We will provide an update on the progress within one hour.

Identified: Our team has been able to confirm that new automation events should now be processed correctly.

We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

Identified: The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

Identified: Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

Investigating: At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

Resolved: All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

Identified: Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.

Identified: It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.

Identified: Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

Investigating: We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Investigating: We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available

Resolved: On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.

Monitoring: We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

Monitoring: The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

Identified: We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Investigating: We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Resolved: We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

Identified: Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

Identified: While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident.

We will provide an update on the progress within one hour.

Identified: Our team has been able to confirm that new automation events should now be processed correctly.

We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

Identified: The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

Identified: Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

Investigating: At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

Resolved: All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

Identified: Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.

Identified: It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.

Identified: Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

Investigating: We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Investigating: We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available

Resolved: On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.

Monitoring: We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

Monitoring: The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

Identified: We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Investigating: We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Resolved: We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

Identified: Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

Identified: While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident.

We will provide an update on the progress within one hour.

Identified: Our team has been able to confirm that new automation events should now be processed correctly.

We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

Identified: The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

Identified: Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

Investigating: At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

Resolved: All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

Identified: Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.

Identified: It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.

Identified: Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

Investigating: We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Investigating: We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available

Resolved: On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.

Monitoring: We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

Monitoring: The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

Identified: We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Investigating: We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Resolved: We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

Identified: Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

Identified: While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident.

We will provide an update on the progress within one hour.

Identified: Our team has been able to confirm that new automation events should now be processed correctly.

We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

Identified: The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

Identified: Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

Investigating: At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

Resolved: All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

Identified: Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.

Identified: It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.

Identified: Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

Investigating: We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Investigating: We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available

Resolved: On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.

Monitoring: We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

Monitoring: The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

Identified: We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Investigating: We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Resolved: We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

Identified: Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

Identified: While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident.

We will provide an update on the progress within one hour.

Identified: Our team has been able to confirm that new automation events should now be processed correctly.

We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

Identified: The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

Identified: Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

Investigating: At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

Resolved: All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

Identified: Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.

Identified: It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.

Identified: Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

Investigating: We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Investigating: We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available

Resolved: On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.

Monitoring: We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

Monitoring: The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

Identified: We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Investigating: We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Resolved: We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

Identified: Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

Identified: While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident.

We will provide an update on the progress within one hour.

Identified: Our team has been able to confirm that new automation events should now be processed correctly.

We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

Identified: The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

Identified: Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

Investigating: At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

Resolved: All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

Identified: Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.

Identified: It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.

Identified: Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

Investigating: We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Investigating: We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available

Resolved: On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.

Monitoring: We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

Monitoring: The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

Identified: We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Investigating: We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Resolved: We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

Identified: Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

Identified: While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident.

We will provide an update on the progress within one hour.

Identified: Our team has been able to confirm that new automation events should now be processed correctly.

We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

Identified: The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

Identified: Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

Investigating: At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

Resolved: All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

Identified: Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.

Identified: It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.

Identified: Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

Investigating: We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Investigating: We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available

Resolved: On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.

Monitoring: We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

Monitoring: The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

Identified: We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Investigating: We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Resolved: We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

Identified: Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

Identified: While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident.

We will provide an update on the progress within one hour.

Identified: Our team has been able to confirm that new automation events should now be processed correctly.

We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

Identified: The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

Identified: Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

Investigating: At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

Resolved: All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

Identified: Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.

Identified: It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.

Identified: Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

Investigating: We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Investigating: We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available

Resolved: On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team.

We apologise for the disruption and thank you for your patience.

Monitoring: We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

Monitoring: The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

Identified: We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Identified: We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

Investigating: We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Resolved: We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed.

Identified: Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

Identified: While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident.

We will provide an update on the progress within one hour.

Identified: Our team has been able to confirm that new automation events should now be processed correctly.

We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour.

Identified: The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available.

Identified: Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time.

Investigating: At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

Resolved: All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

Monitoring: Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

Identified: Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

At this time, Atlassian customers should also be able to once again raise support requests with our team.

We will provide further update within an hour as we are able to progress mitigating this issue.

Identified: It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

We are continuing to receive reports about expanded product impact resulting from this incident.

While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

We will provide further update within one hour, or sooner as further information becomes available.

Identified: Further confirmations of impacted products have now been added to the incident.

Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

Investigating: We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Investigating: We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available