- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on RudderStack. 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 0m it lasted.
Anything that failed between 2026-04-08 13:55 UTC and 2026-04-08 13:55 UTC may need a replay.Subscribe to RudderStack's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=rudderstack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from RudderStack 1
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-fbe55c1b19
Is RudderStack still down?
No, this incident was resolved 2026-04-08 13:55 UTC. For RudderStack's live state, see https://down.guide/rudderstack.
How long did it last?
0m, from 2026-04-08 13:55 UTC to 2026-04-08 13:55 UTC, by the times RudderStack posted.
What caused it?
RudderStack hasn't published a root cause. If it does, it shows here.
Where does this come from?
RudderStack's official status page, https://status.rudderstack.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.