Rewindex

CompaniesSegmentIncidents

Segment: Amazon Kinesis Stream delays

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

AWS outage, Aug 29, 2024 · 14 vendors, 14 incidents

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

“…Amazon Kinesis Stream delays Delivery delays to Amazon Kinesis of over an hour due to AWS outage.…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSSegment, Ably, Front1 to 4 hours later2 vendors, 1 blamed AWSConfluent, SemgrepSegment (this incident)posted +0 min
AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSSegment, Ably, Front1 to 4 hours later2 vendors, 1 blamed AWSConfluent, SemgrepSegment (this incident)posted +0 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/>3 vendors, 1 blamed AWS<br/>Segment, Ably, Front"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 1 blamed AWS<br/>Confluent, Semgrep"]:::blames
  root --> h4
  me["Segment (this incident)<br/>posted +0 min"]:::me
  h1 --- 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

    Delivery delays to Amazon Kinesis of over an hour due to AWS outage.

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

Segment profileRecent Segment incidentsMarkdownJSON