- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 14of 100
What to do
Check whether your product depends on Hookdeck. 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 12m it lasted.
Anything that failed between 2026-06-16 14:09 UTC and 2026-06-16 14:21 UTC may need a replay.Subscribe to Hookdeck's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=hookdeck works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Hookdeck 2
- update
We're seeing increased latency in event delivery and are investigating the root cause.
provider
- resolved
From 2:09 pm UTC to 2:20 pm UTC, we experience increased delivery latency (p99 of ~5 minutes at its worst). A DB switchover, which is normally transparent and doesn't impact latency, left some workers in a crashed state and failed to recover automatically. We're looking into the root cause of why the workers crashed and did not recover.
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-be6b148a9c
Is Hookdeck still down?
No, this incident was resolved 2026-06-16 14:21 UTC. For Hookdeck's live state, see https://down.guide/hookdeck.
How long did it last?
12m, from 2026-06-16 14:09 UTC to 2026-06-16 14:21 UTC, by the times Hookdeck posted.
What caused it?
Hookdeck hasn't published a root cause. If it does, it shows here.
Where does this come from?
Hookdeck's official status page, https://status.hookdeck.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.