- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 31of 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 6h 12m it lasted.
Anything that failed between 2026-01-12 19:23 UTC and 2026-01-13 01:35 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
Some HTTP request sent via custom domains with CNAME to hkdk.events are triggered Cloudflare DDoS protection leading to the requests being blocked. This appeared to be a false positive on Cloudflare end and their engineering team has escalated the issue. Users who have their own DNS configured with Cloudflare reported that disabling the "proxy" on their domain and using it as a custom domain with Hookdeck resolved the issue.
provider
- resolved
The issue hasn't occurred since 1:35 UTC, but we are actively monitoring and investigating the root cause with the CF team
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-475d8fce2d
Is Hookdeck still down?
No, this incident was resolved 2026-01-13 01:35 UTC. For Hookdeck's live state, see https://down.guide/hookdeck.
How long did it last?
6h 12m, from 2026-01-12 19:23 UTC to 2026-01-13 01:35 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.