Atlassian incident · via Jira Service Desk

Some users experiencing issues viewing boards and work items

Major Resolved View vendor source →

Atlassian experienced a major incident on June 9, 2026 affecting Jira Service Management Web, lasting 12h 58m. The incident has been resolved; the full update timeline is below.

Started
Jun 09, 2026, 05:29 AM UTC
Resolved
Jun 09, 2026, 06:27 PM UTC
Duration
12h 58m
Detected by Pingoru
Jun 09, 2026, 05:29 AM UTC

Affected components

Jira Service Management Web

Update timeline

  1. investigating Jun 09, 2026, 05:29 AM UTC

    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.

  2. identified Jun 09, 2026, 06:21 AM UTC

    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.

  3. identified Jun 09, 2026, 06:22 AM UTC

    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.

  4. identified Jun 09, 2026, 09:26 AM UTC

    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.

  5. identified Jun 09, 2026, 09:27 AM UTC

    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.

  6. identified Jun 09, 2026, 10:20 AM UTC

    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.

  7. identified Jun 09, 2026, 10:21 AM UTC

    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.

  8. monitoring Jun 09, 2026, 10:36 AM UTC

    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.

  9. resolved Jun 09, 2026, 06:27 PM UTC

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