Cribl Outage History

Cribl is up right now

Pingoru has recorded 50 incidents for Cribl: 8 in the last 12 months and 3 in the last 90 days.

Source: status.cribl.cloud

50incidents recorded
8last 12 months
3last 90 days
15 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Cribl in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026222 of 720 (3%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 2026121 of 744 (3%)
September 2026255 of 720 (8%)
October 202600 of 519 (0%)

Incidents, newest first

Major September 18, 2026 Cribl Insights showing incomplete data 2h 6m

Started Sep 18, 2026, 07:46 PM UTC· resolved Sep 18, 2026, 09:52 PM UTC

  1. investigating Sep 18, 2026, 07:46 PM UTC

    We are currently investigating this issue.

  2. investigating Sep 18, 2026, 08:05 PM UTC

    We are actively investigating an issue causing Insights to display We are actively investigating an issue causing Insights to display incomplete metric reports. Our team is working to isolate the root cause. We will provide our next update at the top of the hour or as soon as we have more details.

  3. investigating Sep 18, 2026, 09:08 PM UTC

    We are actively investigating an issue causing Insights to display incomplete metric reports. Our team is working to isolate the root cause. We will provide our next update at the top of the hour or as soon as we have more details.

  4. resolved Sep 18, 2026, 09:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 16, 2026 OAuth secret expressions fail to resolve during authentication after 4.20.0 upgrade 2d 4h

Started Sep 16, 2026, 02:52 PM UTC· resolved Sep 18, 2026, 07:41 PM UTC

  1. investigating Sep 16, 2026, 02:52 PM UTC

    We are currently investigating this issue.

  2. investigating Sep 16, 2026, 03:33 PM UTC

    Investigating: We are continuing to investigate an issue that may prevent OAuth secret expressions on Microsoft Sentinel destinations from resolving during authentication following the 4.20.0 upgrade.

  3. investigating Sep 16, 2026, 04:34 PM UTC

    Update: We are continuing our investigation regarding this issue.

  4. identified Sep 16, 2026, 05:44 PM UTC

    The issue has been identified and a fix is being implemented.

  5. monitoring Sep 16, 2026, 05:57 PM UTC

    We have published a known issue with a workaround for this issue. See https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-45304

  6. monitoring Sep 16, 2026, 06:23 PM UTC

    Mitigated: We have identified the issue affecting OAuth secret expressions following the 4.20.0 upgrade and published a Known Issue with a workaround. Customers experiencing authentication failures can follow the documented workaround. Known Issue can be found here: https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-45304

  7. resolved Sep 18, 2026, 07:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 20, 2026 OAuth secrets containing C.* expressions fail to resolve during authentication 21h 17m

Started Aug 20, 2026, 06:13 PM UTC· resolved Aug 21, 2026, 03:30 PM UTC

  1. identified Aug 20, 2026, 06:13 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Aug 20, 2026, 07:12 PM UTC

    We have identified the root cause of the issue impacting OAuth secret fields following the v4.19.1 release. Our engineering team is actively working on a resolution.If you are experiencing this issue or require assistance, please reach out to our support team at [email protected]. Next Update: In 1 hour or as soon as new information becomes available.

  3. identified Aug 20, 2026, 08:01 PM UTC

    We have identified the root cause of the issue impacting OAuth secret fields following the v4.19.1 release. Our engineering team is actively working on a resolution.If you are experiencing this issue or require assistance, please reach out to our support team at [email protected]. Next Update: In 1 hour or as soon as new information becomes available.

  4. identified Aug 20, 2026, 09:01 PM UTC

    We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected]. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.

  5. identified Aug 20, 2026, 09:02 PM UTC

    We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected]. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.

  6. identified Aug 20, 2026, 10:00 PM UTC

    We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected]. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.

  7. identified Aug 20, 2026, 11:10 PM UTC

    We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected]. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.

  8. identified Aug 21, 2026, 12:00 AM UTC

    We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected]. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.

  9. identified Aug 21, 2026, 01:00 AM UTC

    We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected]. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.

  10. identified Aug 21, 2026, 01:47 AM UTC

    We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release. A fix has been prepared and will be deployed as part of a rolling upgrade. Your organization will be picked up for upgrade on a rolling basis between 01:45 and 05:45 UTC on August 21, 2026 (9:45 PM – 1:45 AM EDT, Aug 20–21). Once the upgrade begins for your tenant, it will take approximately 20 minutes to complete. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443): https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at [email protected].

  11. monitoring Aug 21, 2026, 01:49 AM UTC

    A fix has been implemented and we are monitoring the results.

  12. resolved Aug 21, 2026, 03:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 22, 2026 Volume drop in Insights Metrics post 4.17.1 Upgrade 20h 40m

Started Apr 22, 2026, 10:18 PM UTC· resolved Apr 23, 2026, 06:59 PM UTC

  1. investigating Apr 22, 2026, 10:18 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 22, 2026, 10:19 PM UTC

    We are currently investigating an issue where some metrics in Insights are appearing incomplete. Customer data remains secure and unaffected. We are working toward a resolution and will provide the next update at the top of the hour.

  3. investigating Apr 22, 2026, 10:19 PM UTC

    We are currently investigating an issue where some metrics in Insights are appearing incomplete. Customer data remains secure and unaffected. We are working toward a resolution and will provide the next update at the top of the hour.

  4. monitoring Apr 22, 2026, 10:39 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Apr 22, 2026, 10:42 PM UTC

    A fix has been implemented. Metrics are currently backfilling, and we anticipate all data will be available by the top of the hour. No further impact is expected.

  6. resolved Apr 23, 2026, 06:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 22, 2026 Some Cribl Cloud workspaces have data plane workers with incorrect product versions 1h 12m

Started Apr 22, 2026, 01:51 PM UTC· resolved Apr 22, 2026, 03:03 PM UTC

  1. investigating Apr 22, 2026, 01:51 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 22, 2026, 01:51 PM UTC

    Some workspaces are experiencing data plane workers with incorrect product versions and minimal impact to the data plane. The team is currently investigating and triaging the issue.

  3. identified Apr 22, 2026, 01:52 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Apr 22, 2026, 02:57 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Apr 22, 2026, 03:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 11, 2026 Increase in errors in code function following 4.17.0 release 22h 50m

Started Mar 11, 2026, 07:48 PM UTC· resolved Mar 12, 2026, 06:39 PM UTC

  1. investigating Mar 11, 2026, 07:48 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 11, 2026, 07:49 PM UTC

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the top of the hour.

  3. investigating Mar 11, 2026, 08:01 PM UTC

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the half hour.

  4. investigating Mar 11, 2026, 08:38 PM UTC

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the top of the hour.

  5. investigating Mar 11, 2026, 08:56 PM UTC

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the half hour.

  6. investigating Mar 11, 2026, 09:33 PM UTC

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the top of the hour.

  7. investigating Mar 12, 2026, 04:46 AM UTC

    We have confirmed that the recent increase in Code Function errors did not impact overall data flow. We identified an issue with recursive Code Function executions temporarily blocking throughput for a small number of customers. We have worked directly with the affected users to mitigate and stabilize their pipelines, and systems are operating as expected at this time and we are contiuing to monitor all signals.

  8. monitoring Mar 12, 2026, 04:47 AM UTC

    A fix has been implemented and we are monitoring the results.

  9. resolved Mar 12, 2026, 06:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 22, 2026 Cribl cloud is not accessible 1h 47m

Started Feb 22, 2026, 05:02 PM UTC· resolved Feb 22, 2026, 06:49 PM UTC

  1. investigating Feb 22, 2026, 05:02 PM UTC

    We are currently investigating this issue.

  2. investigating Feb 22, 2026, 05:18 PM UTC

    Cribl's ID Provider has an active incident. They have idenitfied their issue. We are monitoring their systems for full services to return. There is no impact to data managed by Cribl. During this incident, scheduled searches may fail to exicute.

  3. investigating Feb 22, 2026, 05:20 PM UTC

    Cribl's ID Provider has an active incident. They have idenitfied their issue. We are monitoring their systems for full services to return. There is no impact to data managed by Cribl. During this incident, scheduled searches may fail to execute.

  4. identified Feb 22, 2026, 05:28 PM UTC

    The issue has been identified and a fix is being implemented.

  5. identified Feb 22, 2026, 05:32 PM UTC

    Cribl's ID Provider has an active incident. They have idenitfied their issue. We are monitoring their systems for full services to return. There is no impact to data managed by Cribl. During this incident, scheduled searches may fail to execute.

  6. identified Feb 22, 2026, 05:35 PM UTC

    We are continuing to monitor the status of our Identity Provider's services.

  7. identified Feb 22, 2026, 06:02 PM UTC

    Our Identity Providers status remains unchanged. We continue to track the resolution of the ongoing incident and the restoration of services.

  8. identified Feb 22, 2026, 06:49 PM UTC

    The status of our Identity Provider has returned to 'Operational.' The incident regarding authentication is now resolved, and all systems are functioning as expected. We continue to track service health as part of our post-resolution oversight.

  9. resolved Feb 22, 2026, 06:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 16, 2025 Cribl.Cloud login issue 37m

Started Nov 16, 2025, 08:21 PM UTC· resolved Nov 16, 2025, 08:59 PM UTC

  1. identified Nov 16, 2025, 08:21 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Nov 16, 2025, 08:22 PM UTC

    We have identified a potential service degradation to Cribl.Cloud logins; caused by an issue identified with our authentication provider. We will update this status page regularly.

  3. resolved Nov 16, 2025, 08:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025 Cribl.Cloud is Experiencing Multiple Degraded Services and Capabilities 1d Organization & Workspace Management

Started Oct 20, 2025, 04:23 PM UTC· resolved Oct 21, 2025, 04:38 PM UTC

  1. identified Oct 20, 2025, 04:23 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Oct 20, 2025, 04:36 PM UTC

    - Cribl.Cloud impacted by AWS outage - Cribl is aware of the following impacts as a result of the ongoing incident in our cloud service provider AWS. Cribl is doing everything within our power to identify impacted services and notify customers. We have limited capacity to remediate impacts as a result of the outage in our underlying service providers. This outage is impacting both Cribl.Cloud and Cribl.Cloud Government. - User Impact - Changes in AWS Customers may not be able to make changes to their Cribl Cloud environments for operations involving the creation or modification of Cribl hosted worker groups, creation of new workspaces. Existing WGs may not provision new instance Some existing Cribl managed worker groups may see individual workers that are down or unhealthy and cannot be relaunched. Customers may see reduced capacity for these worker groups. Status Page Cribl’s status page (status.cribl.cloud) is working intermittently as it relies on AWS Services.

  3. identified Oct 20, 2025, 04:59 PM UTC

    Cribl Engineering continues to monitor and track AWS service health. At this time, there is no change in behavior.

  4. identified Oct 20, 2025, 05:46 PM UTC

    Cribl Engineering have identified Cribl Search as well as Cribl Cloud Hosted Workers in us-east-1 is affected. We will continue to track service health and provide updates on the hour.

  5. identified Oct 20, 2025, 06:58 PM UTC

    We are continuing to monitor service health and availability. Cribl Cloud Search and data plane remain impacted. We will provide another update on the hour.

  6. identified Oct 20, 2025, 07:40 PM UTC

    Cribl has identified impacts to our login systems that are preventing users from logging into Cribl Cloud.

  7. identified Oct 20, 2025, 08:23 PM UTC

    Cribl Engineering continues to monitor and track service health. Cribl Cloud Search, Stream, and Lake remain degraded at this time. We are currently aware of the following impacts: Cribl Logins Cribl has identified impacts to our login systems that are preventing users from logging into Cribl Cloud. Changes in AWS Customers may not be able to make changes to their Cribl Cloud environments for operations involving the creation or modification of Cribl hosted worker groups, creation of new workspaces. Existing WGs may not provision new instances Some existing Cribl managed worker groups may see individual workers that are down or unhealthy and cannot be relaunched. Customers may see reduced capacity for these worker groups. Status Page Cribl's status page (status.cribl.cloud) is working intermittently as it relies on AWS Services. Cribl University Account Creation Cribl has identified issues with the creation of new Cribl U accounts. Cribl Search Cribl Search users may experience limited availability. Cribl Lake Creation or modification of Lake resources may fail.

  8. identified Oct 20, 2025, 10:03 PM UTC

    Cribl Engineering have confirmed reports that Scheduled Searches are impacted and may not run when expected. We will continue to monitor services health and reliability, and will provide another update on the hour.

  9. identified Oct 20, 2025, 11:05 PM UTC

    Cribl Engineering continues to monitor and track AWS service health. Our teams are working to restore affected Cribl services.

  10. monitoring Oct 21, 2025, 01:14 AM UTC

    A fix has been implemented and we are monitoring the results.

  11. monitoring Oct 21, 2025, 01:25 AM UTC

    All Cribl services have been restored. Cribl Engineering continues to monitor service health and have moved to a "Mitigated" status. If you see further issues, please reach out to "[email protected]" for assistance. Future updates will follow as we move towards a "Resolved" status.

  12. resolved Oct 21, 2025, 04:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 13, 2025 Some S3 destinations are experiencing issues 1d 23h

Started Aug 13, 2025, 04:15 PM UTC· resolved Aug 15, 2025, 04:01 PM UTC

  1. identified Aug 13, 2025, 04:15 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Aug 13, 2025, 04:29 PM UTC

    The following issues with the Amazon S3 Destination are currently being investigated: S3 buckets with 'Object Lock' enabled will fail and S3 Destinations configured without a region set may experience issues.

  3. identified Aug 13, 2025, 06:35 PM UTC

    We are currently and testing the fix to the S3 destination issues with object locks enabled and when region is not specified.

  4. monitoring Aug 13, 2025, 07:27 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Aug 13, 2025, 07:32 PM UTC

    We have identified the root cause for both "S3 buckets object lock" and "region is not specified" errors. Both issues were mitigated for Cloud workers. Please check S3 destination statuses for Hybrid Worker Groups and Edge Nodes, that have been upgraded for 4.13.1, to verify whether S3 destinations are impacted by this issue.

  6. monitoring Aug 13, 2025, 07:33 PM UTC

    We have identified the root cause for both "S3 buckets object lock" and "region is not specified" errors. Both issues were mitigated for Cloud workers. Please check S3 destination statuses for Hybrid Worker Groups and Edge Nodes, that have been upgraded for 4.13.1, to verify whether S3 destinations are impacted by this issue.

  7. monitoring Aug 14, 2025, 04:31 AM UTC

    Customers who use AWS SQS sources may experience S3 bucket ingestion issues for buckets that are located in a different geographic region than the SQS queue. This issue has been mitigated for Cloud Workers. We do not recommend upgrading Hybrid Workers to 4.13.1 at this time.

  8. monitoring Aug 14, 2025, 05:19 PM UTC

    We will perform a critical upgrade to Cribl Cloud organizations between 09:00 and 12:00 UTC on Friday, August 15th, 2025. An email has been sent to Cribl Cloud users with full details. If you have not yet enabled auto-upgrade on your Hybrid Workers, please manually upgrade them to 4.13.2 once your organization has been upgraded.

  9. resolved Aug 15, 2025, 04:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 11, 2025 A limited population of Cribl Cloud organizations are experiencing disruptions to the control and data plane 39m

Started Aug 11, 2025, 03:52 PM UTC· resolved Aug 11, 2025, 04:31 PM UTC

  1. identified Aug 11, 2025, 03:52 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Aug 11, 2025, 03:52 PM UTC

    A limited population of Cribl Cloud organizations are experiencing disruptions to their control and data planes. Some control plane services (such as Cribl Search) may be in a degraded state and certain data flows may be impacted. We are actively investigating and remediating the issue to impacted customers. Cribl support will proactively reach out to impacted customers. Please be on the lookout for an email to the owners of the organization.

  3. monitoring Aug 11, 2025, 04:21 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 11, 2025, 04:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 23, 2025 High CPU utilization on Lakehouses 3d Cribl Lake

Started Jun 23, 2025, 06:24 PM UTC· resolved Jun 26, 2025, 06:29 PM UTC

  1. investigating Jun 23, 2025, 06:24 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 23, 2025, 06:26 PM UTC

    We're currently investigating an issue with high CPU utilization on small Lakehouses. No customer action required at this time. If you are impacted, you will see delayed or failing searches to Lakehouse.

  3. investigating Jun 23, 2025, 07:35 PM UTC

    Update: We have restarted the impacted Lakehouses, which is allowing them to slowly return to a normal state. There is still no Customer action required at this time. Investigating: We are still in the process of investigating a long-term resolution, and the incident is still active.

  4. identified Jun 23, 2025, 08:46 PM UTC

    The issue has been identified and a fix is being implemented.

  5. monitoring Jun 23, 2025, 08:48 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. monitoring Jun 24, 2025, 04:01 PM UTC

    Update: The impacted tenants have been restarted, and are being actively monitored for the impact-thresholds. We will proactively intervene if necessary, but tenants should be performing as expected. Investigating: Engineering has identified the trigger and is finalizing long-term remediation plans.

  7. identified Jun 26, 2025, 12:56 PM UTC

    The issue has been identified and a fix is being implemented.

  8. identified Jun 26, 2025, 06:08 PM UTC

    Cribl will be performing an Emergency Maintenance at 2pm ET and 4pm ET in order to remediate this Incident. During this time, Customers should expect small windows of slow searches from Cribl Search to Lakehouse datasets during this time. If your Lakehouse does not perform as expected after this time, please contact Cribl Support for assistance.

  9. monitoring Jun 26, 2025, 06:29 PM UTC

    A fix has been implemented and we are monitoring the results.

  10. resolved Jun 26, 2025, 06:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 28, 2025 Investigation of potential performance regression in Search –

Started Apr 28, 2025, 10:24 PM UTC· resolved Apr 28, 2025, 10:24 PM UTC

  1. resolved Apr 28, 2025, 10:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 23, 2025 Login loop when logging into cribl.cloud 3h 9m Login & Registration

Started Apr 23, 2025, 03:57 PM UTC· resolved Apr 23, 2025, 07:06 PM UTC

  1. investigating Apr 23, 2025, 03:57 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 23, 2025, 03:59 PM UTC

    Cribl teams have identified that customers are unable to access their tenants. They are faced with a screen waiting for the page load.

  3. monitoring Apr 23, 2025, 03:59 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. investigating Apr 23, 2025, 03:59 PM UTC

    We are currently investigating this issue.

  5. investigating Apr 23, 2025, 03:59 PM UTC

    Cribl teams have identified that customers are unable to access their tenants. They are faced with a screen waiting for the page load.

  6. monitoring Apr 23, 2025, 04:00 PM UTC

    A fix has been implemented and we are monitoring the results.

  7. monitoring Apr 23, 2025, 04:01 PM UTC

    Status Page Update: Login Access Restored for Cribl Cloud We experienced a temporary login disruption for Cribl Cloud that has now been resolved. Our team successfully identified and mitigated the issue by rolling back an orchistration configuration. All customers should now be able to access their tenants normally. We apologize for any inconvenience and thank you for your patience during this brief service interruption. Key Details: - Impact: Login & Registration temporarily unavailable - Duration: Approximately 15 minutes - Current Status: Full service restored - Actions Taken: Rolled back to previous stable service version We recommend attempting to log in again. If you continue to experience any issues, please contact our support team.

  8. monitoring Apr 23, 2025, 04:02 PM UTC

    Status Page Update: Login Access Restored for Cribl Cloud We experienced a temporary login disruption for Cribl Cloud that has now been resolved. Our team successfully identified and mitigated the issue by rolling back an orchestration configuration. All customers should now be able to access their tenants normally. We apologize for any inconvenience and thank you for your patience during this brief service interruption. Key Details: - Impact: Login & Registration temporarily unavailable - Duration: Approximately 15 minutes - Current Status: Full service restored - Actions Taken: Rolled back to previous stable service version We recommend attempting to log in again. If you continue to experience any issues, please contact our support team.

  9. resolved Apr 23, 2025, 07:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 14, 2025 Cribl.cloud Authentication Slowness 1h 34m Login & Registration

Started Apr 14, 2025, 10:54 PM UTC· resolved Apr 15, 2025, 12:29 AM UTC

  1. identified Apr 14, 2025, 10:54 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Apr 14, 2025, 11:09 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 15, 2025, 12:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 20, 2025 Some Cribl Cloud Control Plane features are degraded 1d 4h

Started Feb 20, 2025, 06:25 PM UTC· resolved Feb 21, 2025, 10:32 PM UTC

  1. identified Feb 20, 2025, 06:25 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Feb 20, 2025, 06:26 PM UTC

    We're currently experiencing issues with Cribl Cloud infrastructure management functions. Users may encounter problems when attempting to create/update Worker Groups & Workspaces. Important: There is no impact on data processing. Our team is actively investigating and working to resolve this issue. We'll provide updates as soon as we have more information.

  3. monitoring Feb 21, 2025, 01:39 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. identified Feb 21, 2025, 10:26 AM UTC

    The issue has been identified and a fix is being implemented.

  5. identified Feb 21, 2025, 08:08 PM UTC

    We have identified a issue with control plane in Cribl.Cloud and will be applying a hotfix at 4pm ET today, with no interruption. There is no impact to data processing or regular use of Cribl.Cloud. Users may encounter trouble with the following: - Provisioning new worker groups within an existing workspace - modify existing worker groups within an existing workspace

  6. resolved Feb 21, 2025, 10:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 29, 2025 Cribl Cloud Emergency Worker Maintenance 1h 23m

Started Jan 29, 2025, 06:41 PM UTC· resolved Jan 29, 2025, 08:05 PM UTC

  1. identified Jan 29, 2025, 06:41 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Jan 29, 2025, 06:41 PM UTC

    We are performing urgent maintenance on Cribl Cloud to replace instances of affected worker nodes. Data processing will continue uninterrupted during remediation actions.

  3. resolved Jan 29, 2025, 08:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 8, 2025 Cloud portal not accessible 11m

Started Jan 08, 2025, 03:14 PM UTC· resolved Jan 08, 2025, 03:25 PM UTC

  1. identified Jan 08, 2025, 03:14 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Jan 08, 2025, 03:15 PM UTC

    This issue has been mitigated. Customers should be able to access the Cloud Portal now.

  3. monitoring Jan 08, 2025, 03:15 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Jan 08, 2025, 03:17 PM UTC

    This issue has been mitigated. Customers should be able to access the Cloud Portal now.

  5. resolved Jan 08, 2025, 03:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 6, 2024 Multiple organizations did not upgrade during 4.9.1 cloud release 2h 23m

Started Nov 06, 2024, 02:49 PM UTC· resolved Nov 06, 2024, 05:13 PM UTC

  1. investigating Nov 06, 2024, 02:49 PM UTC

    We are currently investigating this issue.

  2. investigating Nov 06, 2024, 02:52 PM UTC

    We have identified some Cribl Cloud Organizations have not yet upgraded to version 4.9.1 and are investigating the root cause further. Some users may see version 4.9.0 still active, and may also experience some UI refreshes as we work to resolve the version upgrade. Please contact '[email protected]' if you have any questions or concerns.

  3. investigating Nov 06, 2024, 03:48 PM UTC

    Cribl Cloud Engineering are diligently working to upgrade the remaining Cloud Organizations to version 4.9.1. We will continue to provide updates here, but please feel free to contact '[email protected]' if you have any immediate questions or concerns.

  4. investigating Nov 06, 2024, 04:39 PM UTC

    We have identified the issue affecting some Cribl Cloud Organizations from upgrading to version 4.9.1. We are now addressing the last few Organizations and will post a progress update shortly.

  5. investigating Nov 06, 2024, 05:10 PM UTC

    Cribl Engineering have successfully upgraded the affected Organizations to version 4.9.1.

  6. resolved Nov 06, 2024, 05:13 PM UTC

    This incident has been resolved.

Read the full incident report →