C1 Outage History

Started Oct 28, 2026, 02:27 PM UTC· resolved Oct 28, 2026, 03:05 PM UTC

1. investigating Oct 28, 2026, 02:27 PM UTC

   We are investigating an incident where customers may experience issues with step-up authentication. Normal ticket processing is not affected. We will provide further updates within 30 minutes.

2. identified Oct 28, 2026, 02:58 PM UTC

   We have identified an issue where customers are experiencing issues with approval tasks that require step-up-authentication. We are deploying a fix, and will provide an additional update within 30 minutes.

3. resolved Oct 28, 2026, 03:05 PM UTC

   We have resolved an incident where C1 customers experienced issues with approval tasks that required step-up-authentication. Please reach out to support if you have any concerns.

Read the full incident report →

Started Oct 22, 2026, 08:30 PM UTC· resolved Oct 22, 2026, 09:03 PM UTC

1. investigating Oct 22, 2026, 08:30 PM UTC

   We are investigating possible impact where some customers in the US may be experiencing issues with the C1 web application and connectors. We will provide further updates within 30 minutes.

2. monitoring Oct 22, 2026, 08:43 PM UTC

   We are monitoring the issue. We have not identified impact to customers at this time.

3. resolved Oct 22, 2026, 09:03 PM UTC

   The issue is now resolved. We have determined that customers were not affected.

Read the full incident report →

Started Sep 17, 2026, 09:08 PM UTC· resolved Sep 17, 2026, 09:46 PM UTC

1. investigating Sep 17, 2026, 09:08 PM UTC

   We are investigating an issue causing errors and delays in ticket and workflow processing. We will provide further updates within 30 minutes.

2. monitoring Sep 17, 2026, 09:20 PM UTC

   We have deployed a fix and are actively monitoring system health. We will provide an additional update within 30 minutes.

3. resolved Sep 17, 2026, 09:46 PM UTC

   We have resolved an incident where C1 customers in the US instance experienced elevated errors and delays in ticket processing, notifications, and automations. We have confirmed all services are operating normally. We will conduct a full post-incident review to understand the root cause and identify opportunities to prevent similar issues in the future. If you have any questions or concerns, please contact our support team.

Read the full incident report →

Started Sep 15, 2026, 02:34 PM UTC· resolved Sep 15, 2026, 04:07 PM UTC

1. investigating Sep 15, 2026, 02:34 PM UTC

   We are investigating reports that the "Submit" button on the access request form is greyed out for some users and apps.

2. identified Sep 15, 2026, 03:18 PM UTC

   We have identified the issue causing the "Submit" button on access request forms to be disabled for some users and apps and are working on a fix.

3. resolved Sep 15, 2026, 04:07 PM UTC

   We have resolved an incident that prevented submitting access requests on some cloud infrastructure application entitlements.

Read the full incident report →

Started Sep 03, 2026, 10:12 PM UTC· resolved Sep 04, 2026, 12:12 AM UTC

1. investigating Sep 03, 2026, 10:12 PM UTC

   Due to the ongoing AWS outage, we are experiencing broader service impacts across the C1 platform. Potential impacts may include delayed syncs and other intermittent service disruptions. We are monitoring the situation closely and will provide updates as more information becomes available.

2. investigating Sep 03, 2026, 10:27 PM UTC

   We are continuing to monitor the impact of the AWS outage and will provide updates as we learn more. Please reach out to Support if you have any questions.

3. monitoring Sep 03, 2026, 11:24 PM UTC

   We are no longer seeing an active impact to the C1 platform. We are continuing to monitor the situation closely until AWS confirms the outage is fully resolved. We will provide an additional update as more information becomes available. Please reach out to Support if you have any questions.

4. resolved Sep 04, 2026, 12:12 AM UTC

   We are no longer seeing any impact on the C1 platform, and all services are operating normally.

Read the full incident report →

Started Aug 24, 2026, 10:22 PM UTC· resolved Aug 24, 2026, 11:12 PM UTC

1. investigating Aug 24, 2026, 10:22 PM UTC

   We are investigating an issue where customers may be experiencing issues with Functions. We will provide further updates within 30 minutes.

2. monitoring Aug 24, 2026, 10:32 PM UTC

   We have identified and deployed a fix for an issue where some customers were experiencing C1 Function Invocation Errors. We are actively monitoring the system to confirm the issue has been fully resolved. We will provide an additional update within 30 minutes

3. resolved Aug 24, 2026, 11:12 PM UTC

   We have resolved an incident where customers experienced issues with C1 functions. Please reach out to support if you have any concerns.

Read the full incident report →

Started Aug 17, 2026, 06:25 PM UTC· resolved Aug 17, 2026, 08:23 PM UTC

1. investigating Aug 17, 2026, 06:25 PM UTC

   We are investigating the issue.

2. monitoring Aug 17, 2026, 06:34 PM UTC

   We are monitoring the results. Impacted functionality is being restored. We will continue to monitor and will share a final update once we confirm the issue is fully resolved.

3. resolved Aug 17, 2026, 08:23 PM UTC

   We have resolved an incident where C1 customers experienced issues whee c1 was inaccessible. Please reach out to support if you have any concerns.

Read the full incident report →

Started Aug 13, 2026, 05:45 PM UTC· resolved Aug 13, 2026, 06:13 PM UTC

1. investigating Aug 13, 2026, 05:45 PM UTC

   We are investigating an issue that is causing some requests to our API to timeout. We will provide further updates in 30 minutes.

2. resolved Aug 13, 2026, 06:13 PM UTC

   We have resolved an incident where requests to our API were failing due to timeouts. Impacted users may have experienced timeouts in the C1 web application, and notifications and automations may have been delayed. We will be conducting a full investigation. Please reach out to support if you have any concerns.

Read the full incident report →

Started Aug 10, 2026, 08:08 PM UTC· resolved Aug 11, 2026, 02:32 PM UTC

1. investigating Aug 10, 2026, 08:08 PM UTC

   We are investigating an issue where a small number of connectors are not syncing successfully. We will provide further updates within 30 minutes.

2. identified Aug 10, 2026, 08:43 PM UTC

   We have identified an issue where some customers are experiencing a small number of connectors not syncing successfully. We are actively working to mitigate this issue. We will provide an additional update within 30 minutes.

3. monitoring Aug 10, 2026, 09:17 PM UTC

   We have deployed a fix for an issue where some customers were experiencing a small number of connectors not syncing successfully. We are actively monitoring the system to confirm the issue has been fully resolved.

4. resolved Aug 11, 2026, 02:32 PM UTC

   We have resolved an incident where C1 customers experienced a small number of connectors not syncing successfully. Please reach out to support if you have any concerns.

Read the full incident report →

Started Jul 30, 2026, 04:13 PM UTC· resolved Jul 30, 2026, 04:59 PM UTC

1. investigating Jul 30, 2026, 04:13 PM UTC

   We have received several reports of unable to access C1 tenants. Our team is currently investigating.

2. identified Jul 30, 2026, 04:22 PM UTC

   We identified the issue and are currently working on a fix. We will update the incident once the fix is deployed!

3. identified Jul 30, 2026, 04:29 PM UTC

   We are currently deploying a fix and will have an update shortly.

4. monitoring Jul 30, 2026, 04:43 PM UTC

   We have deployed a fix and confirmed UI access is restored. We are currently monitoring.

5. resolved Jul 30, 2026, 04:59 PM UTC

   We have resolved an incident caused by errors in our API. A recent optimization to the API introduced an issue that affected access to the application via web browsers, Terraform, the CLI, and MCP integrations. No customer data was impacted, and automations, connector syncs and provisioning continued to operate normally throughout the incident. We have confirmed that all services are operating normally. We will conduct a full post-incident review to understand the root cause and identify opportunities to prevent similar issues in the future. If you have any questions or concerns, please contact our support team.

Read the full incident report →

Started Jul 21, 2026, 05:20 PM UTC· resolved Jul 21, 2026, 10:57 PM UTC

1. investigating Jul 21, 2026, 05:20 PM UTC

   We are investigating an issue affecting file imports. Impacted customers may see a "No attributes found" message under User data sources, and replacing a file may result in profile attributes being removed. As a precaution, we recommend avoiding file replacements until this issue is resolved. We are actively investigating the issue and will provide further updates as they become available.

2. identified Jul 21, 2026, 05:48 PM UTC

   We identified the issue affecting file imports, and a fix is in progress. As a precaution, we still recommend avoiding file replacements until this issue is fully resolved. We will provide further updates as they become available.

3. identified Jul 21, 2026, 07:35 PM UTC

   The fix is currently being deployed. As a precaution, we still recommend avoiding file replacements until this issue is fully resolved. We will provide further updates as they become available.

4. monitoring Jul 21, 2026, 09:13 PM UTC

   The fix has been deployed, and we are monitoring the issue.

5. resolved Jul 21, 2026, 10:57 PM UTC

   Profile attribute processing is now working as expected for File imports. The issue is now resolved.

Read the full incident report →

Started Jul 20, 2026, 09:58 PM UTC· resolved Jul 20, 2026, 11:02 PM UTC

1. identified Jul 20, 2026, 09:58 PM UTC

   We have identified an issue where manually configured entitlements that use match_baton_id are not merging correctly with connector-discovered entitlements during syncs. This can result in provisioning failures with the error: "Process post policy provisioning failed with error: unsupported provisioner." We are actively working to mitigate this issue.

2. monitoring Jul 20, 2026, 10:48 PM UTC

   A fix for this issue has been deployed and is currently being monitored. The entitlements will reconcile automatically on subsequent connector syncs. No action is required.

3. resolved Jul 20, 2026, 11:02 PM UTC

   We have confirmed that the issue is resolved following completion of the sync. The issue is now fully resolved.

Read the full incident report →

Started Jul 16, 2026, 04:59 PM UTC· resolved Jul 16, 2026, 05:05 PM UTC

1. investigating Jul 16, 2026, 04:59 PM UTC

   We are investigating elevated errors rates in the C1 platform. We will provide further updates within 30 minutes.

2. resolved Jul 16, 2026, 05:05 PM UTC

   We have resolved an incident related to elevated error rates in the C1 platform. Please reach out to support if you experience any further issues.

Read the full incident report →

Started Jul 16, 2026, 01:10 PM UTC· resolved Jul 16, 2026, 03:07 PM UTC

1. investigating Jul 16, 2026, 01:10 PM UTC

   We are aware that a subset of customers are experiencing sync failures with certain connectors. Our team is actively investigating the issue and working to restore normal service as quickly as possible.

2. identified Jul 16, 2026, 01:23 PM UTC

   We have identified the root cause of the sync failures affecting a subset of customers using certain connectors. Our team is actively working on a fix and will provide another update as soon as more information is available. We appreciate your patience as we work to restore normal service.

3. monitoring Jul 16, 2026, 02:56 PM UTC

   The fix has been deployed, and we are seeing sync activity return to normal. We are continuing to monitor the affected connectors closely to ensure the issue is fully resolved. We will provide another update once monitoring is complete.

4. resolved Jul 16, 2026, 03:07 PM UTC

   The issue affecting syncs for a subset of customers using certain connectors has been resolved. We have confirmed that sync activity has returned to normal, and we appreciate your patience throughout this incident.

Read the full incident report →

Started Jun 23, 2026, 11:24 PM UTC· resolved Jun 23, 2026, 11:24 PM UTC

1. resolved Jun 23, 2026, 11:24 PM UTC

   An internal change affecting sync stats triggered data drop alerts that are invalid. No data has been lost, and no action is required. These notifications will automatically be dismissed by the next sync.

Read the full incident report →

Started Jun 23, 2026, 10:35 PM UTC· resolved Jun 23, 2026, 10:53 PM UTC

1. investigating Jun 23, 2026, 10:35 PM UTC

   We are investigating an issue where users are unable to submit Access Requests from the UI. Requests should go through as expected via Slack. We will provide further updates as soon as possible.

2. resolved Jun 23, 2026, 10:53 PM UTC

   The issue has been identified and resolved following the deployment of a fix. We have confirmed that everything is working as expected. Please reach out to support if you have any concerns.

Read the full incident report →

Started Jun 23, 2026, 02:59 AM UTC· resolved Jun 23, 2026, 06:47 AM UTC

1. identified Jun 23, 2026, 02:59 AM UTC

   We have identified an issue where some customers are experiencing grants being incorrectly deleted. We've rolled back changes to stop impact. We are investigating next steps in each case. We will provide an additional update as soon as possible.

2. identified Jun 23, 2026, 04:32 AM UTC

   We are continuing to establish next steps in remediation.

3. resolved Jun 23, 2026, 06:47 AM UTC

   We have resolved an incident that caused some C1 customers to temporarily lose application grants. As a result, affected customers may have experienced loss and re-enrollment of group and access profile membership. Certify tasks targeting the affected grants were also cancelled. We have fixed the underlying issue and are actively restoring cancelled certify tasks. We will provide impacted customers with a summary of membership changes and affected certify tasks within 12 hours. Please contact support with any questions or concerns.

Read the full incident report →

Started Jun 19, 2026, 12:10 AM UTC· resolved Jun 19, 2026, 01:17 AM UTC

1. investigating Jun 19, 2026, 12:10 AM UTC

   We're investigating an issue impacting a small number of customers related to Policy Routing pointing at deleted policies.

2. identified Jun 19, 2026, 12:24 AM UTC

   We identified the issue.

3. resolved Jun 19, 2026, 01:17 AM UTC

   We have resolved an incident where a small subset of C1 customers experienced an issue where stale configuration rules were pointing at deleted policies. Please reach out to to support if you have any concerns.

Read the full incident report →

Started May 18, 2026, 11:45 AM UTC· resolved May 18, 2026, 01:20 PM UTC

1. investigating May 18, 2026, 11:45 AM UTC

   We are investigating an incident where all customers may be experiencing issues requesting entitlements through the C1 Slack app. Impacted customers may be unable to request access through the Slack app. Requesting access through the UI is not impacted. We are investigating the issue.

2. identified May 18, 2026, 12:35 PM UTC

   We have identified the issue and are working on a fix. We’ll provide an update once the issue is deployed.

3. monitoring May 18, 2026, 01:02 PM UTC

   We have deployed a fix and are actively monitoring the system to confirm the issue has been fully resolved.

4. resolved May 18, 2026, 01:20 PM UTC

   We have resolved an incident where C1 customers experienced issues with requesting access through the Slack App. Please reach out to to support if you have any concerns.

Read the full incident report →

Started Apr 20, 2026, 07:21 PM UTC· resolved Apr 20, 2026, 09:54 PM UTC

1. investigating Apr 20, 2026, 07:21 PM UTC

   We are currently investigating reports of performance degradation that may impact some customers’ ability to assign entitlements to access profiles. Affected users may encounter DEADLINE_EXCEEDED errors when attempting to assign an entitlement to an access profile. Other areas of the platform may also be impacted. Our team is actively working to identify the root cause and will provide further updates as more information becomes available.

2. monitoring Apr 20, 2026, 08:22 PM UTC

   Our team has deployed changes to and is actively monitoring system performance to ensure the impact has been resolved.

3. monitoring Apr 20, 2026, 09:15 PM UTC

   Our team has deployed additional changes and will continue to monitor system performance to ensure the impact has been resolved.

4. resolved Apr 20, 2026, 09:54 PM UTC

   We have resolved an incident where some C1 customers experienced performance degradation when attempting to assign an entitlement to an access profile. Please reach out to to support if you have any concerns.

Read the full incident report →

Started Apr 18, 2026, 06:49 PM UTC· resolved Apr 18, 2026, 07:28 PM UTC

1. identified Apr 18, 2026, 06:49 PM UTC

   We have identified an issue causing timeouts when loading access profiles on some tenants. We are working to resolve this and will provide an update within 60 minutes.

2. resolved Apr 18, 2026, 07:28 PM UTC

   The issue is now resolved. We will continue to monitor application performance. Please reach out to our support team if you have any questions or concerns.

Read the full incident report →

Started Apr 18, 2026, 02:06 AM UTC· resolved Apr 18, 2026, 06:03 AM UTC

1. identified Apr 18, 2026, 02:06 AM UTC

   We have identified an issue where all customers are experiencing delays in data processing. These delays are affecting data accuracy, access requests, notifications, and ticket actions. We are actively working to mitigate this issue. We will provide an additional update within 60 minutes.

2. monitoring Apr 18, 2026, 03:05 AM UTC

   We have deployed a fix for an issue where all customers were experiencing delays in data processing. We are seeing improvements in data processing speeds, and we are actively monitoring the situation. We will provide an additional update within 60 minutes.

3. monitoring Apr 18, 2026, 04:05 AM UTC

   We are continuing to see improvements in data processing speeds. We are actively monitoring the situation and will provide an additional update within 60 minutes.

4. monitoring Apr 18, 2026, 05:08 AM UTC

5. resolved Apr 18, 2026, 06:03 AM UTC

   We have resolved an incident where all customers were experiencing delays in data processing. We will continue to monitor the situation. Please reach out to our support team if you have any questions or concerns.

Read the full incident report →

Started Apr 02, 2026, 07:29 PM UTC· resolved Apr 02, 2026, 08:01 PM UTC

1. investigating Apr 02, 2026, 07:29 PM UTC

   We are investigating a possible incident where some customers may be experiencing issues with V1 Connectors. Impacted customers may see failed syncs on their V1 connectors. V2 connectors are currently not impacted. We will provide further updates within 30 minutes.

2. resolved Apr 02, 2026, 08:01 PM UTC

   We have identified the issue is not widespread and is limited to a subset of specific V1 connectors. We're contacting those affected directly and will mark this incident resolved.

Read the full incident report →