- Level
- confirmed
- Worst impact
- Degraded
- Components
- Content Agent
- Down Index
- 22of 100
What to do
Check whether you use Sanity Content Agent. 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 5h 56m it lasted.
Anything that failed between 2026-05-29 09:19 UTC and 2026-05-29 15:14 UTC may need a replay.Subscribe to Sanity's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=sanity works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Sanity 4
- investigating
We are aware of an issue with the Content Agent in Dashboard where a small number of responses in longer-running threads may not be delivered to the user. We are investigating and will provide an update shortly.
provider
- identified
The issue has been identified and we are working on a fix.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has now been resolved.
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-4d72540ea5
Is Sanity still down?
No, this incident was resolved 2026-05-29 15:14 UTC. For Sanity's live state, see https://down.guide/sanity.
How long did it last?
5h 56m, from 2026-05-29 09:19 UTC to 2026-05-29 15:14 UTC, by the times Sanity posted.
What was affected?
Sanity named Content Agent.
What caused it?
Sanity hasn't published a root cause. If it does, it shows here.
Where does this come from?
Sanity's official status page, https://www.sanity-status.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.