Is Hookdeck Down?

No — Hookdeck is up

Hookdeck's status page: Not available · we could not read it
FlareWarden checks: Website reachable · 8 of 8 regions · 188 ms

Right now

We could not read Hookdeck's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

hookdeck.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 188 ms
Checked: 1 hour ago

By region

Amsterdam reachable, 201 ms
Dallas reachable, 258 ms
Frankfurt reachable, 106 ms
Newark reachable, 168 ms
Paris reachable, 225 ms
Stockholm reachable, 128 ms
Sydney reachable, 193 ms
Toronto reachable, 226 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	35 ms	5 ms	20 ms	173 ms
Dallas	46 ms	0 ms	57 ms	179 ms
Frankfurt	26 ms	1 ms	8 ms	77 ms
Newark	58 ms	9 ms	15 ms	124 ms
Paris	34 ms	10 ms	29 ms	167 ms
Stockholm	50 ms	1 ms	14 ms	101 ms
Sydney	137 ms	1 ms	7 ms	183 ms
Toronto	34 ms	11 ms	29 ms	134 ms

We check that hookdeck.com loads, not every feature behind it. Test it yourself

History

Hookdeck website availability

Measured by FlareWarden · hookdeck.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 235ms

Last 30 days

59-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of hookdeck.com from multiple regions every 6 hours. Hookdeck's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 59 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Hookdeck itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Hookdeck goes down

We check Hookdeck every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required