OFFLINE
Awaiting data
Atlassian service status
InforesolvedCloud

Delayed SCIM provisioning syncs of users and groups from Identity Providers

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.

Started

Jan 9, 2024, 10:03 PM UTC

Resolved

Jan 12, 2024, 5:13 PM UTC

Duration

3d

InvestigatingJan 9, 10:03 PM

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.

MonitoringJan 10, 3:17 AM

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.

MonitoringJan 10, 7:56 PM

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

MonitoringJan 11, 6:54 PM

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.

MonitoringJan 11, 10:36 PM

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.

MonitoringJan 12, 6:55 AM

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.

ResolvedJan 12, 5:13 PM

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.