Rewindex

CompaniesGustoIncidents

Gusto: We appreciate your patience as we are experiencing longer than anticipated wait times

MinorStatus: resolvedStarted Resolved (56 min)2 updatesstspg.io (opens in new tab)
Part of an outage event

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

Gusto’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +20 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

same windowAWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSDagster, Snowflake, Vanta1 to 4 hours later7 vendors, 5 blamed AWSAmplitude, Temporal Cloud, Coralogix, Confluent +3Gusto (this incident)posted +20 min
same windowAWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSDagster, Snowflake, Vanta1 to 4 hours later7 vendors, 5 blamed AWSAmplitude, Temporal Cloud,Coralogix, Confluent +3Gusto (this incident)posted +20 min
Gusto 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["Gusto (this incident)<br/>posted +20 min"]:::me
  root -.->|"same window"| 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.

Affected components: Chat SystemPhone SystemEmail System

Timeline of updates

  1. identified

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

  2. resolved

    This incident has been resolved.

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

Gusto profileRecent Gusto incidentsMarkdownJSON