Hookdeck incident

Outpost outage

Resolved on May 20, 2026, affecting section-319547 (API) and section-319547 (Delivery).

resolved May 20, 2026, 06:00 AM UTC

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.

Started
May 20, 2026, 06:00 AM UTC
Resolved
May 20, 2026, 06:00 AM UTC
Duration
–
Detected by Pingoru
May 20, 2026, 06:00 AM UTC

Affected components

section-319547 (API)section-319547 (Delivery)

Update timeline

  1. resolved May 20, 2026, 06:00 AM UTC

    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.

Your product runs on more than Hookdeck

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →