Jira Service Management Status

Resolved: On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions.

We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.

Identified: We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions.

Our engineering team is actively working on a resolution. We will provide an update within the next hour.

Investigating: We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.

Resolved: The issue has now been resolved, and the service is operating normally for all affected customers.

Monitoring: Our team has been able to apply the fix and mitigate the issue. The services have been restored to normal operations.

We will continue to actively monitor over the next 8 hours to confirm stability.

Identified: Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.

We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

Identified: Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.

We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

Identified: Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.

We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

Identified: Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.

We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

Identified: Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.

We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

Identified: Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.

We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

Investigating: We are investigating reports of intermittent errors and degredated performance for some Jira Service Management and Jira Cloud customers. We will provide further updates within one hour.

Resolved: We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.

We apologize for any inconvenience that this issue may have caused.

Monitoring: Our team has now determined that performance has returned to expected levels for those impacted by this incident.

Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.

We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

Identified: Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.

At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.

We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

Investigating: We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.

Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

Resolved: On June 10 2026, between 08:10 and 09:08 UTC, users experienced degraded performance and inability to load the Assets page, which is impacting the ability to create, update, and delete assets.

We have implemented a fix and services have been restored to normal operation for all affected customers.

Investigating: Users are facing degraded performance while accessing Assets page which is impacting Assets object creation, updation and deletion activities. Our teams are investigating actively and will be sharing more details in next 1 hour.

Resolved: We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.

We apologize for any inconvenience that this issue may have caused.

Monitoring: Our team has now determined that performance has returned to expected levels for those impacted by this incident.

Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.

We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

Identified: Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.

At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.

We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

Investigating: We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.

Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

Resolved: We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.

We apologize for any inconvenience that this issue may have caused.

Monitoring: Our team has now determined that performance has returned to expected levels for those impacted by this incident.

Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.

We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

Identified: Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.

At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.

We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

Investigating: We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.

Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

Resolved: We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.

We apologize for any inconvenience that this issue may have caused.

Monitoring: Our team has now determined that performance has returned to expected levels for those impacted by this incident.

Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.

We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

Identified: Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.

At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.

We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

Investigating: We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.

Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

Resolved: We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.

We apologize for any inconvenience that this issue may have caused.

Monitoring: Our team has now determined that performance has returned to expected levels for those impacted by this incident.

Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.

We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

Identified: Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.

At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.

We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

Investigating: We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.

Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

Resolved: We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.

We apologize for any inconvenience that this issue may have caused.

Monitoring: Our team has now determined that performance has returned to expected levels for those impacted by this incident.

Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.

We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

Identified: Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.

At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.

We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

Investigating: We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.

Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

Resolved: We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.

We apologize for any inconvenience that this issue may have caused.

Monitoring: Our team has now determined that performance has returned to expected levels for those impacted by this incident.

Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.

We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

Identified: Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.

At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.

We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

Investigating: We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.

Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

Resolved: On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions.

We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.

Identified: We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions.

Our engineering team is actively working on a resolution. We will provide an update within the next hour.

Investigating: We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.

Resolved: We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.

We apologize for any inconvenience that this issue may have caused.

Monitoring: Our team has now determined that performance has returned to expected levels for those impacted by this incident.

Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.

We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

Identified: Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.

At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.

We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

Investigating: We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.

Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

Resolved: We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.

We apologize for any inconvenience that this issue may have caused.

Monitoring: Our team has now determined that performance has returned to expected levels for those impacted by this incident.

Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.

We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

Identified: Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.

At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.

We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

Investigating: We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.

Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

Resolved: We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.

We apologize for any inconvenience that this issue may have caused.

Monitoring: Our team has now determined that performance has returned to expected levels for those impacted by this incident.

Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.

We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

Identified: Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.

At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.

We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

Investigating: We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.

Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

Resolved: We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.

We apologize for any inconvenience that this issue may have caused.

Monitoring: Our team has now determined that performance has returned to expected levels for those impacted by this incident.

Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.

We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

Identified: Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.

At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.

We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

Investigating: We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.

Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

Resolved: We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.

We apologize for any inconvenience that this issue may have caused.

Monitoring: Our team has now determined that performance has returned to expected levels for those impacted by this incident.

Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.

We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

Identified: Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.

At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.

We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

Investigating: We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.

Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.