Skip to main content
Hookdeck logo

Is Hookdeck Down?

No — Hookdeck is up

Reachable from all 8 checked regions

Average response time: 188ms

Last checked · checks run every 6 hours

Official status page: https://status.hookdeck.com

Hookdeck uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
167ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 13 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

13-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: no data
Sep 3: no data
Sep 4: no data
Sep 5: no data
Sep 6: no data
Sep 7: no data
Sep 8: 100.00% uptime, 16 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 24 checks
Sep 13: 100.00% uptime, 24 checks
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 24 checks
Sep 17: 100.00% uptime, 24 checks
Sep 18: 100.00% uptime, 31 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

dfw
273ms
DNS 40ms TCP 1ms TLS 55ms TTFB 218ms
ewr
102ms
DNS 19ms TCP 1ms TLS 18ms TTFB 84ms
fra
106ms
DNS 34ms TCP 1ms TLS 9ms TTFB 86ms
gru
192ms
DNS 122ms TCP 1ms TLS 7ms TTFB 169ms
iad
184ms
DNS 61ms TCP 1ms TLS 9ms TTFB 113ms
jnb
247ms
DNS 51ms TCP 1ms TLS 61ms TTFB 185ms
lax
241ms
DNS 144ms TCP 1ms TLS 24ms TTFB 213ms
lhr
160ms
DNS 76ms TCP 2ms TLS 9ms TTFB 127ms

What Hookdeck does

Hookdeck is an event gateway that sits between webhook providers and the applications consuming them. It ingests events over HTTP, queues them, and delivers them to your endpoints with retries, rate limiting and filtering, keeping a searchable record of every attempt. Teams use it so that a provider like Stripe or Shopify never has to reach their servers directly.

What an outage looks like

Webhooks stop arriving at your endpoints while the providers sending them report success, because Hookdeck accepted the event and delivery is what stalled. Nothing in your application errors, so the symptom is work that silently never happens rather than a failure. The dashboard may not load, leaving you unable to inspect or replay events even when delivery is healthy.

What to do about it

Read status.hookdeck.com, which separates Request Ingestion (HTTP) from Event Delivery within its Event Gateway group, and reports Retries, Issues, Metrics Export, the Admin API and the Dashboard as their own components. If Event Delivery is the affected row, events are being held rather than lost and will deliver when it recovers, so do not ask providers to resend. If Request Ingestion is affected, ask providers to replay from their side instead.

Is it down for everyone, or just you?

If this page says Hookdeck is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Stripe
Stripe
Shopify
Shopify
Inngest
Inngest
Ably
Ably

Hookdeck outage FAQ

My provider says the webhook was delivered but my app never received it. Is Hookdeck down?
That is exactly the shape of an Event Delivery incident. Hookdeck reports Request Ingestion and Event Delivery as separate components, so it can accept an event and return success to Stripe or Shopify while the onward delivery to your endpoint stalls. The provider's logs show success because their delivery target was Hookdeck. Check the Event Delivery row before investigating your own endpoint.
Will events be lost during a Hookdeck outage?
Events that reached Request Ingestion are recorded, so a delivery incident normally means delayed rather than dropped. Hookdeck does not publish a guarantee covering every failure mode, so confirm against the incident's own updates and your event list once it clears. Avoid asking providers to resend during the window, because the held events and the resent ones will both deliver and your endpoint must be idempotent.
Should I point my webhooks directly at my own servers during an outage?
Only as a considered fallback, and rarely mid-incident. Changing the destination at a provider takes effect for new events and does not move ones already held at Hookdeck, so you can end up with events split across two paths and delivered out of order. If Event Delivery is affected the queue drains on recovery, which is usually less disruptive than reconfiguring providers under pressure.
The Hookdeck dashboard will not load. Are my webhooks still being delivered?
Probably, and they are reported separately. Hookdeck lists Dashboard under its Clients and Frontend group, apart from the Event Gateway components that do the work. Losing the dashboard means you cannot inspect, filter or replay events, not that delivery has stopped. Avoid issuing bulk retries you cannot observe until it comes back.
How do I tell a Hookdeck outage from my endpoint returning errors?
Look at where the attempts stop. If Hookdeck recorded delivery attempts and your endpoint returned 4xx or 5xx, that is your side and Hookdeck's retry policy applies. If no attempts were made at all, the platform side is the place to look. status.hookdeck.com reports Retries and Issues as their own components, so an incident on either changes how failures are handled.

How we measure this

  • We request Hookdeck's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Hookdeck publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Hookdeck goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required