Cribl experienced a notice incident on March 27, 2023, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Mar 27, 2023, 10:15 AM UTC
January 12, 2022 | 12:34AM We are still working to completely resolve the cert issue for the tenants we identified as impacted. At this time we are seeing progress in obtaining valid certs and communicating with our ssl cert provider. We are waiting to see the cert rotation process complete and verify tenant health checks and data throughput have returned to normal. The anticipated duration for this process is roughly 20 minutes. No new impact or additional users impacted have been identified outside of the initial set our monitoring alerted us on. Another update will be published in 20-30 minutes. January 11, 2022 | 11:29PM We are still working to resolve the cert issue for the tenants we identified as impacted. Root cause still points to inconsistencies with communicating with our ssl cert provider. A workaround is being looked at. No new impacts or scope of users impacted has been identified yet, our team is double-checking this as we also look to remediate for the initial tenants that our alerting informed us of. We appreciate your patience if you were one of the tenants impacted. We will update again in 30 minutes. January 11, 2022 | 10:27PM Update on impact: Data throughput for the 10 impacted tenants appears to be effected as well. If you were one of the 10 tenants you would not be able to reach your LogStream from Cloud and Worker throughput would be halted during this time. January 11, 2022 | 10:10PM We are still working on remediation those 10 impacted tenants. All tenants impacted have been contacted and informed. At this point it looks like there might have been a communication issue with our cert provider but we are still verifying what we believe to be the root cause. A new update will arrive in 30 minutes. January 11, 2022 | 09:29PM The Cribl Cloud Ops team is investigating an issue where ssl certs expired on a small number of our tenant population (<10). If your tenant was affected the impact of this would be an inability to access your LogStream leader from Cribl Cloud. We are still investigating and working towards remediation. Another update will be posted in 30 minutes.