Rewindex

CompaniesSegmentIncidents

Segment: Delay in Amazon S3 destinations

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

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

Segment’s incident names AWS / us-east-1 (location or integration). (hop 1, posted +4 h 1 min vs the first vendor naming AWS)

“…Delay in Amazon S3 destinations We observed significant improvements in error rate for the Amazon S3 destination uploading data to S3 buckets located in the us-east-1 region.…”

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, DopplerSegment (this incident)posted +4 h 1 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, DopplerSegment (this incident)posted +4 h 1 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 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["Segment (this incident)<br/>posted +4 h 1 min"]:::me
  later --- 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

    We observed significant improvements in error rate for the Amazon S3 destination uploading data to S3 buckets located in the us-east-1 region.

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