Atlassian incident

Delayed SCIM provisioning syncs of users and groups from Identity Providers

Notice Resolved View vendor source →

Atlassian experienced a notice incident on January 9, 2024, lasting 2d 19h. The incident has been resolved; the full update timeline is below.

Started
Jan 09, 2024, 10:03 PM UTC
Resolved
Jan 12, 2024, 05:13 PM UTC
Duration
2d 19h
Detected by Pingoru
Jan 09, 2024, 10:03 PM UTC

Update timeline

  1. investigating Jan 09, 2024, 10:03 PM UTC

    We are investigating cases of degraded performance when SCIM provisioning users/groups for Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Access Cloud customers. We will provide more details shortly.

  2. monitoring Jan 10, 2024, 03:17 AM UTC

    We have identified a bottleneck in the Group synchronisation process for SCIM Provisioning. We have increased the resources allocated to the process in order to mitigate the issue. We are now monitoring the service.

  3. monitoring Jan 10, 2024, 07:56 PM UTC

    The bottleneck in the Group synchronization process for SCIM Provisioning is still under work. We are closely monitoring the service.

  4. monitoring Jan 11, 2024, 06:54 PM UTC

    The bottleneck in the Group synchronization process for SCIM Provisioning is still under work. The team is all hands on deck to improve the situation.

  5. monitoring Jan 11, 2024, 10:36 PM UTC

    The bottleneck in the Group synchronization process for SCIM Provisioning has seen considerable improvement due to recent changes, but it is still under work. The team is all hands on deck to keep improving the situation.

  6. monitoring Jan 12, 2024, 06:55 AM UTC

    A fix for the bottleneck identified in the Group synchronization process for SCIM Provisioning has been made. We are seeing processing start to return to normal levels and will be monitoring over the next few hours. The team is all hands on deck to keep improving the situation.

  7. resolved Jan 12, 2024, 05:13 PM UTC

    We experienced degraded SCIM provisioning from external Identity Providers for Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Access. The issue has been resolved and the service is operating normally.