- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 30of 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 0m it lasted.
Anything that failed between 2026-05-20 06:00 UTC and 2026-05-20 06:00 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 1
- resolved
Between 22:32 UTC on May 19 and 01:39 UTC on May 20, Outpost was fully unavailable for ~3 hours. This affected the publish API, all other API endpoints used to interact with Outpost, and the managed Outpost dashboard. The root cause was an outage at Railway, the upstream infrastructure provider Outpost runs on (their report: https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage). The trigger was external, but Outpost is the layer our customers rely on and the responsibility is ours. We're evaluating changes to our infrastructure setup to reduce single-provider exposure going forward.
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-69f0b058cc
Is Hookdeck still down?
No, this incident was resolved 2026-05-20 06:00 UTC. For Hookdeck's live state, see https://down.guide/hookdeck.
How long did it last?
0m, from 2026-05-20 06:00 UTC to 2026-05-20 06:00 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.