Atlassian Customer Service Management Outage History

Atlassian Customer Service Management is up right now

Atlassian Customer Service Management had 5 outages in the last 2 years totaling 30h 3m of downtime — averaging 0.2 incidents per month.

There were 5 Atlassian Customer Service Management outages since February 20, 2026 totaling 30h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://customer-service-management.status.atlassian.com

Minor June 10, 2026

Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps

Detected by Pingoru
Jun 10, 2026, 06:14 AM UTC
Resolved
Jun 10, 2026, 06:31 AM UTC
Duration
17m
Affected: Customer experienceCustomer Service Management AI agentSupport websiteEmail requestCustomer Service Management spacesCustomer profilesAutomation for Jira
Timeline · 4 updates
  1. investigating Jun 10, 2026, 06:14 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.

  2. identified Jun 10, 2026, 06:14 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.

  3. 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.

  4. 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.

Read the full incident report →

Minor February 20, 2026

Degraded performance of Cloud Products when selecting users or teams

Detected by Pingoru
Feb 20, 2026, 07:13 AM UTC
Resolved
Feb 20, 2026, 12:26 PM UTC
Duration
5h 12m
Affected: Customer experienceCustomer Service Management AI agentSupport websiteEmail requestCustomer Service Management spacesCustomer profilesAutomation for Jira
Timeline · 3 updates
  1. identified Feb 20, 2026, 07:13 AM UTC

    We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

  2. identified Feb 20, 2026, 12:26 PM UTC

    We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

  3. resolved Feb 20, 2026, 12:26 PM UTC

    This issue has been resolved and all services are functional.

Read the full incident report →