# Cribl: Critical incident: Cribl.Cloud is Experiencing Multiple Degraded Services and Capabilities **Summary:** _summary pending_ ## Part of an outage event - [AWS us-east-1 outage, Oct 20, 2025: 141 vendors, 181 incidents](https://rewindex.com/events/2025-10-20-aws-us-east-1) - This incident blames AWS as the cause. (hop 1, posted +9 h 12 min vs AWS’s own post) - Evidence: “…ure updates will follow as we move towards a "Resolved" status. - Cribl.Cloud impacted by AWS outage - Cribl is aware of the following impacts as a result of the ongoing incident in our cloud service…” ```mermaid flowchart LR root["AWS us-east-1
posted 07:11 UTC"]:::root before["Posted before AWS did
5 vendors, 4 blamed AWS
Salesforce, Descope, Ashby +2"]:::blames root --> before h1["Within an hour
18 vendors, 17 blamed AWS
Asana, Firebolt, Monday.com +15"]:::blames root --> h1 h4["1 to 4 hours later
30 vendors, 29 blamed AWS
SingleStore, Loops, Buildkite +27"]:::blames root --> h4 later["Later
45 vendors, 44 blamed AWS
RudderStack, Airbyte, Unbounce +42"]:::blames root --> later p0["Twilio
posted +15 min"]:::blames root --> p0 k0["BigCommerce
+2 h 46 min"]:::hop2 p0 -->|"blamed Twilio"| k0 p1["Webflow
posted +4 h 37 min, did not name AWS"]:::timing root -.-> p1 k1["Rootly
+10 h 23 min"]:::hop2 p1 -->|"blamed Webflow"| k1 p2["Baseten
posted +4 min"]:::blames root --> p2 k2["Zed
+26 h 20 min"]:::hop2 p2 -->|"blamed Baseten"| k2 me["Cribl (this incident)
posted +9 h 12 min"]:::me later --- me ``` _Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._ - Kind: Major incident · Label: critical (vendor) - Changed: 2025-10-20 16:23 UTC · Detected: 2026-10-19 18:33 UTC - [Source: https://stspg.io/frhpmzrb63ct](https://stspg.io/frhpmzrb63ct) - [Company: Cribl](https://rewindex.com/company/cribl.md) - Versions: before (none: first archived) → after incident\_version:731/hk97x9g0g5jt@7f504e4147e3 - Change 1 of 1 for this incident Incident page (full timeline): [Cribl.Cloud is Experiencing Multiple Degraded Services and Capabilities](https://rewindex.com/company/cribl/incidents/hk97x9g0g5jt.md) ## What changed **1. Added: Title** ```diff + Cribl.Cloud is Experiencing Multiple Degraded Services and Capabilities ``` **2. Added: Impact** ```diff + critical ``` **3. Added: Status** ```diff + resolved ``` **4. Added: Start time** ```diff + 2025-10-20 16:23 UTC ``` **5. Added: Resolved time** ```diff + 2025-10-21 16:38 UTC ``` **6. Added: Affected components** ```diff + Global - Organization & Workspace Management, Organization & Workspace Management ``` **7. Added: Update** (identified) · 2025-10-20 16:23 UTC ```diff + The issue has been identified and a fix is being implemented. ``` **8. Added: Update** (identified) · 2025-10-20 16:36 UTC ```diff + - 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. ``` **9. Added: Update** (identified) · 2025-10-20 16:59 UTC ```diff + Cribl Engineering continues to monitor and track AWS service health. At this time, there is no change in behavior. ``` **10. Added: Update** (identified) · 2025-10-20 17:46 UTC ```diff + 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. ``` **11. Added: Update** (identified) · 2025-10-20 18:58 UTC ```diff + 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. ``` **12. Added: Update** (identified) · 2025-10-20 19:40 UTC ```diff + Cribl has identified impacts to our login systems that are preventing users from logging into Cribl Cloud. ``` **13. Added: Update** (identified) · 2025-10-20 20:23 UTC ```diff + 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. ``` **14. Added: Update** (identified) · 2025-10-20 22:03 UTC ```diff + 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. ``` **15. Added: Update** (identified) · 2025-10-20 23:05 UTC ```diff + Cribl Engineering continues to monitor and track AWS service health. Our teams are working to restore affected Cribl services. ``` **16. Added: Update** (monitoring) · 2025-10-21 01:14 UTC ```diff + A fix has been implemented and we are monitoring the results. ``` **17. Added: Update** (monitoring) · 2025-10-21 01:25 UTC ```diff + 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 "support@cribl.io" for assistance. Future updates will follow as we move towards a "Resolved" status. ``` **18. Added: Update** (resolved) · 2025-10-21 16:38 UTC ```diff + This incident has been resolved. ``` ## History of this incident | When (UTC) | Change | Label | | --- | --- | --- | | 2025-10-20 16:23 UTC | Critical incident: Cribl.Cloud is Experiencing Multiple Degraded Services and Capabilities (this change) | critical | All Cribl changes: [timeline](https://rewindex.com/company/cribl/changes.md) _Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._ --- Canonical: https://rewindex.com/change/i57a5a7db2b0feb · Markdown: https://rewindex.com/change/i57a5a7db2b0feb.md · JSON: https://rewindex.com/api/v1/changes/i57a5a7db2b0feb · Generated 2026-10-20T00:00:45.462Z