Rewindex

CompaniesCriblIncidents

Cribl: Account registration is failing due to AWS region outage

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.cribl.cloud (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Dec 7, 2021 · 71 vendors, 77 incidents

Cribl’s incident blames AWS as the cause. (hop 1, posted +3 h 21 min vs the first vendor naming AWS)

“…Account registration is failing due to AWS region outage December 07, 2021 | 11:23PM The Cribl Cloud Ops team is observing registrations are completing successfully again and users are able to subsequ…”

Swipe sideways to see the whole diagram.

AWS us-east-1own incident not archivedWithin an hour11 vendors, 9 blamed AWSAptible, Firebolt, Honeycomb +81 to 4 hours later16 vendors, 12 blamed AWSMaven Central, Pusher, Confluent +13Later3 vendors, 2 blamed AWSSegment, Confluent, DopplerCribl (this incident)posted +3 h 21 min
AWS us-east-1own incident not archivedWithin an hour11 vendors, 9 blamed AWSAptible, Firebolt, Honeycomb +81 to 4 hours later16 vendors, 12 blamed AWSMaven Central, Pusher,Confluent +13Later3 vendors, 2 blamed AWSSegment, Confluent, DopplerCribl (this incident)posted +3 h 21 min
Cribl is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS us-east-1<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>11 vendors, 9 blamed AWS<br/>Aptible, Firebolt, Honeycomb +8"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>16 vendors, 12 blamed AWS<br/>Maven Central, Pusher, Confluent +13"]:::blames
  root --> h4
  later["Later<br/>3 vendors, 2 blamed AWS<br/>Segment, Confluent, Doppler"]:::blames
  root --> later
  me["Cribl (this incident)<br/>posted +3 h 21 min"]:::me
  h4 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    December 07, 2021 | 11:23PM The Cribl Cloud Ops team is observing registrations are completing successfully again and users are able to subsequently sign-in. We are moving the incident to a resolved state but continue to monitor the AWS Status page (https://status.aws.amazon.com/) and our own systems for any impairment. December 07, 2021 | 09:40PM The Cribl Cloud Ops team continues to monitor the AWS outage situation (https://status.aws.amazon.com/) and signs that systems have returned to normal operation. At this time we are still seeing an impact on new user registration however no other services are impacted. Please note that if you attempted registration during the incident you will not be required to re-register and should be able to sign-in with the email/password you entered in the registration flow. We will continue to add updates and we thank you for your patience. December 07, 2021 | 07:58PM Due to the ongoing AWS outage (https://status.aws.amazon.com/), we are experiencing failures in our new user registration service. The Cribl Cloud Ops team is monitoring the situation and will provide updates here. No existing users or other services are affected at this time.

From Cribl’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Impact, status and times are the vendor’s own, as last archived. View on status.cribl.cloud (opens in new tab).

Cribl profileRecent Cribl incidentsMarkdownJSON