Rewindex

CompaniesCoralogixIncidents

Coralogix: Intermittent UI issues - US West region (cx498 url accounts) - An AWS regional incident (link inside)

MinorStatus: resolvedStarted Resolved (10 h)1 updatestatus.coralogix.com (opens in new tab)
Part of an outage event

AWS outage, Sep 18, 2023 · 29 vendors, 29 incidents

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

“…Intermittent UI issues - US West region (cx498 url accounts) - An AWS regional incident (link inside) The incident has been fully resolved. Throughout 13 hours of a broad cross AZ, 26 service disrupti…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSDagster, Snowflake, Vanta1 to 4 hours later7 vendors, 5 blamed AWSAmplitude, Temporal Cloud, Coralogix, Confluent +3Coralogix (this incident)posted +1 h 35 min
AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSDagster, Snowflake, Vanta1 to 4 hours later7 vendors, 5 blamed AWSAmplitude, Temporal Cloud,Coralogix, Confluent +3Coralogix (this incident)posted +1 h 35 min
Coralogix is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 1 blamed AWS<br/>Dagster, Snowflake, Vanta"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>7 vendors, 5 blamed AWS<br/>Amplitude, Temporal Cloud, Coralogix, Confluent +3"]:::blames
  root --> h4
  me["Coralogix (this incident)<br/>posted +1 h 35 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

    The incident has been fully resolved. Throughout 13 hours of a broad cross AZ, 26 service disruption in AWS US West2 the system remained operational with Intermittent interruptions and slowness. Most alerts and searches remained operational. Our team will work to learn from this experience and further improve our robustness and ability to withstand cloud service disruptions. For clients with highly critical data, we offer a multi region option (additional charge). Contact your AM for details if this is relevant.

From Coralogix’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.coralogix.com (opens in new tab).

Coralogix profileRecent Coralogix incidentsMarkdownJSON