Incidentsby GlyphDelayed delivery reporting for ReverseETL
Nov 4, 01:09 UTCNov 4, 17:56 UTC
Duration
16h 48m
Impact
Minor
Root cause
Not disclosed
Segment, 90 days
10 incidents
Affected
Reverse ETL (EU)Reverse ETL (US)Reverse ETL - Reverse ETL (EU)Reverse ETL - Reverse ETL (US)
Final update
We've restored the ReverseETL delivery counts in the US
Timeline
- Resolved · Nov 4, 17:56 UTC
We've restored the ReverseETL delivery counts in the US
- Identified · Nov 4, 15:51 UTC
We've restored the ReverseETL delivery counts in the EU and are actively working on updating them in the US.
- Identified · Nov 4, 04:32 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.
- Identified · Nov 4, 01:09 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.
More from Segment
Full historyIntermittent failures scheduling warehouse jobs and processing Profile Syncslasted 2h 15mDelays to Realtime Audiences and Journeyslasted 2h 8mSegment event delivery issueslasted 16h 20mAudience & Journey data delivery delay in EU regionlasted 1h 16mBraze Web Event Delivery is experience event delivery issuelasted 8h 33mActions S3 is currently experience formatting issues with the delivered eventslasted 2h 10m