Delayed delivery reporting for ReverseETL

What to do

• Check whether you use Segment Reverse ETL (EU), Reverse ETL (US) in eu, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 16h 48m it lasted.

  Anything that failed between 2025-11-04 01:09 UTC and 2025-11-04 17:56 UTC may need a replay.

• Subscribe to Segment's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=segment works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Segment 4

1. identifiedNov 4, 2025, 1:09 AM UTC

   ReverseETL delivery counts are currently delayed. Syncs that started between 6:00 AM and 4:00 PM PST on November 3 may show inaccurate counts or timeout errors. We've identified the issue and are working towards a resolution. Note: This is only affecting reporting, no data loss or change in delivery.

   provider

2. identifiedNov 4, 2025, 4:32 AM UTC

   We’re actively working on retroactively updating the ReverseETL delivery counts for affected customers. All ReverseETL Syncs created after 4 PM PST will correctly report counts.

   provider

3. identifiedNov 4, 2025, 3:51 PM UTC

   We've restored the ReverseETL delivery counts in the EU and are actively working on updating them in the US.

   provider

4. resolvedNov 4, 2025, 5:56 PM UTC

   We've restored the ReverseETL delivery counts in the US

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.