🟢 Operational
Delayed SCIM provisioning syncs of users and groups from Identity Providers
Resolved
- Started
- 2024-01-12 17:13 UTC
983 days ago - Last update
- 2024-01-12 17:13 UTC
983 days ago - Duration
- 0s
Timeline
-
12 Jan · 17:13 UTC
🟡 Resolved
atom
Jan 12, 17:13 UTC
Resolved - 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.
Jan 12, 06:55 UTC
Update - 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.
Jan 11, 22:36 UTC
Update - 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.
Jan 11, 18:54 UTC
Update - 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.
Jan 10, 19:56 UTC
Update - The bottleneck in the Group synchronization process for SCIM Provisioning is still under work. We are closely monitoring the service.
Jan 10, 03:17 UTC
Monitoring - 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.
Jan 9, 22:03 UTC
Investigating - 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. -
12 Jan · 17:13 UTC
🟡 Resolved
atom
Jan 12, 17:13 UTC
Resolved - 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.
Jan 12, 06:55 UTC
Update - 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.
Jan 11, 22:36 UTC
Update - 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.
Jan 11, 18:54 UTC
Update - 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.
Jan 10, 19:56 UTC
Update - The bottleneck in the Group synchronization process for SCIM Provisioning is still under work. We are closely monitoring the service.
Jan 10, 03:17 UTC
Monitoring - 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.
Jan 9, 22:03 UTC
Investigating - 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. -
12 Jan · 17:13 UTC
🟡 Resolved
atom
Jan 12, 17:13 UTC
Resolved - 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.
Jan 12, 06:55 UTC
Update - 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.
Jan 11, 22:36 UTC
Update - 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.
Jan 11, 18:54 UTC
Update - 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.
Jan 10, 19:56 UTC
Update - The bottleneck in the Group synchronization process for SCIM Provisioning is still under work. We are closely monitoring the service.
Jan 10, 03:17 UTC
Monitoring - 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.
Jan 9, 22:03 UTC
Investigating - 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.
Source
Official Atlassian status — view original incident ↗
IT Status normalizes vendor wording into a common vocabulary and rewrites machine-shaped titles for readability. The vendor's page remains authoritative.