Delayed SCIM provisioning syncs of users and groups from Identity Providers

What happened

Atlassian's Status Page - Delayed SCIM provisioning syncs of users and groups from Identity Providers.

Summary assembled by rule from the sources below

Timeline

1. 17:13
   First appeared on Atlassian StatusAAtlassian Status

   1. 22:03InvestigatingWe 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. 03:17MonitoringWe 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. 19:56UpdateThe bottleneck in the Group synchronization process for SCIM Provisioning is still under work. We are closely monitoring the service.
   4. 18:54UpdateThe 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. 22:36UpdateThe 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. 06:55UpdateA 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. 17:13ResolvedWe 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.

Sources