- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 30of 100
Summary
Knock says transactional emails sent from its dashboard were not being delivered, and it identified the source as its transactional email provider, Postmark. Knock says a fix has been implemented and it is monitoring the service, though account invites were still degraded and not sending in its 13:10 UTC update.
Written by anthropic/claude-haiku-5.5 from Knock's own updates.
What to do
Check whether your product depends on Knock. 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 2h 21m it lasted.
Anything that failed between 2026-11-06 12:27 UTC and 2026-11-06 14:47 UTC may need a replay.Subscribe to Knock's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=knock works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Knock 5
- investigating
We're investigating reports that transactional emails from the Knock dashboard are not being delivered. We're actively working with our mail provider on a fix.
provider
- identified
We've identified the source of the issue with our transactional email provider (Postmark) and are implementing a fix.
provider
- identified
We're still working on a fix to all transactional emails and mitigating the ongoing spam issue we're dealing with. For the time being, account invites are degraded and are still not sending.
provider
- monitoring
A fix has been implemented, and we're currently monitoring the service.
provider
- resolved
This incident has now been resolved and the service is now fully operational.
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-dda0b5477f
Is Knock still down?
No, this incident was resolved 2026-11-06 14:47 UTC. For Knock's live state, see https://down.guide/knock.
How long did it last?
2h 21m, from 2026-11-06 12:27 UTC to 2026-11-06 14:47 UTC, by the times Knock posted.
What caused it?
Knock hasn't published a root cause. If it does, it shows here.
Where does this come from?
Knock's official status page, https://status.knock.app, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.