Jira Software incident
Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps
Jira Software experienced a minor incident on June 10, 2026 affecting Viewing content and Create and edit and 1 more component, lasting 1h 35m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 10, 2026, 04:55 AM UTC
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.
- identified Jun 10, 2026, 05:39 AM UTC
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.
- monitoring Jun 10, 2026, 06:14 AM UTC
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.
- resolved Jun 10, 2026, 06:31 AM UTC
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.