- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on Ghost(Pro). 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 1h 2m it lasted.
Anything that failed between 2026-03-31 16:38 UTC and 2026-03-31 17:41 UTC may need a replay.Subscribe to Ghost(Pro)'s feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=ghost works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Ghost(Pro) 2
- identified
We've identified an issue with webhooks not being delivered. A fix is in progress
provider
- resolved
A routine infrastructure configuration change inadvertently blocked outbound webhook requests. Because webhooks are delivered once and not retried, any events during the affected window were lost and cannot be replayed. We've rolled out a fix and confirmed webhook delivery is working normally again. We're adding dedicated monitoring for webhook delivery to catch this kind of issue earlier in the future. The affected window was approximately 11:55 UTC to 17:30 UTC, with exact timings differing per site.
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-7b08e68182
Is Ghost(Pro) still down?
No, this incident was resolved 2026-03-31 17:41 UTC. For Ghost(Pro)'s live state, see https://down.guide/ghost.
How long did it last?
1h 2m, from 2026-03-31 16:38 UTC to 2026-03-31 17:41 UTC, by the times Ghost(Pro) posted.
What caused it?
Ghost(Pro) hasn't published a root cause. If it does, it shows here.
Where does this come from?
Ghost(Pro)'s official status page, https://ghoststatus.org, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.