rewindex

CompaniesSegmentIncidents

Segment: Engage Journeys and Broadcasts may intermittently error if using email or SMS content templates.

MinorStatus: resolvedStarted Resolved (45 min)1 updatestatus.segment.com (opens in new tab)
Part of an outage event

AWS outage, Jun 13, 2023 · 29 vendors, 32 incidents

Segment’s incident depends on AWS (declared dependency, named as a cause before); it did not name AWS. (hop 1, posted +2 h 3 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

depends on AWSknown dependencyAWSown incident not archivedWithin an hour13 vendors, 13 blamed AWSPipedream, Wiz, Temporal Cloud, Ashby +91 to 4 hours later7 vendors, 6 blamed AWSCockroachDB, Vanta, Asana, JFrog +3Known dependency9 vendorsUnbounce, Mapbox, Klaviyo, Webflow +5Segment (this incident)posted +2 h 3 min
depends on AWSknown dependencyAWSown incident not archivedWithin an hour13 vendors, 13 blamed AWSPipedream, Wiz, TemporalCloud, Ashby +91 to 4 hours later7 vendors, 6 blamed AWSCockroachDB, Vanta, Asana,JFrog +3Known dependency9 vendorsUnbounce, Mapbox, Klaviyo,Webflow +5Segment (this incident)posted +2 h 3 min
Segment 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/>13 vendors, 13 blamed AWS<br/>Pipedream, Wiz, Temporal Cloud, Ashby +9"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>7 vendors, 6 blamed AWS<br/>CockroachDB, Vanta, Asana, JFrog +3"]:::blames
  root --> h4
  dr["Known dependency<br/>9 vendors<br/>Unbounce, Mapbox, Klaviyo, Webflow +5"]:::hop2
  root -.->|"depends on AWS"| dr
  me["Segment (this incident)<br/>posted +2 h 3 min"]:::me
  root -.->|"known dependency"| 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

    This incident has been resolved.

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

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

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

Cite this

Status incident (vendor impact label: minor) posted by Segment, started 2023-06-13 21:16 UTC, resolved after 45 min, 1 update(s).

Title
Engage Journeys and Broadcasts may intermittently error if using email or SMS content templates.
Vendor
Segment
Date
URL
https://rewindex.com/company/segment/incidents/xkhtdhrrhpt8

Segment profileRecent Segment incidentsAll outages on June 13, 2023Segment in June 2023MarkdownJSON