RudderStack: Facebook Custom Destination Delivery Failure
Timeline of updates
- resolved
Summary:
We experienced an issue affecting the Facebook Custom destination where events were not delivered due to a bug. Event delivery was paused during the window listed above.Impact:
All active connections are rETL connections. Most connections have the "retry failed records" setting enabled — these will automatically deliver missed events during the next scheduled sync. However, connections without retry enabled will require the customer to perform a full sync.Resolution:
The underlying bug has been fixed, and normal event delivery has resumed as of 10 Apr 2026 14:53 GMT.
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a0a827b51e3a4725…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by RudderStack, started 2026-04-08 13:55 UTC, resolved after 0 min, 1 update(s).
- Title
- Facebook Custom Destination Delivery Failure
- Vendor
- RudderStack
- Date
- URL
- https://rewindex.com/company/rudderstack/incidents/rm3z66r8ckt6
RudderStack profileRecent RudderStack incidentsAll outages on April 8, 2026RudderStack in April 2026MarkdownJSON