- Level
- confirmed
- Worst impact
- Major outage
- Components
- Studio
- Down Index
- 44of 100
What to do
Check whether you use Sanity Studio. 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 4h 34m it lasted.
Anything that failed between 2026-10-08 09:55 UTC and 2026-10-08 14:28 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 18
- investigating
We are currently investigating an issue where elevated listener latency may result in slower performance and lag within Sanity Studio for a subset of customers. Our team is actively working to identify the root cause and mitigate the impact. Issue starting around 9:10 UTC.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are currently continuing to investigate the issue, while also rolling out mitigations.
provider
- investigating
We are continuing to investigate the issue. Additionally, there might be a slight delay in document publishes for "scheduled publishing" functionality.
provider
- investigating
We are currently continuing to investigate the issue, while also preparing to roll a set of mitigations.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We're continuing to investigate this issue. In the meantime, we've begun rolling out preliminary measures to mitigate its impact.
provider
- investigating
We're continuing to investigate this issue. And we are continuing rolling out preliminary measures to mitigate its impact.
provider
- investigating
We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact. "scheduled publishing" functionality confirmed unaffected by this incident.
provider
- investigating
We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact.
provider
- investigating
We're continuing to investigate this issue. And we are continuing to apply measures to mitigate its impact.
provider
- identified
The issue has been identified. We are continuing to apply fixes to mitigate its impact.
provider
- identified
We are continuing to apply fixes to mitigate the impact.
provider
- identified
We are continuing to apply fixes to mitigate the impact. No errors have been observed from the changes rolled out so far.
provider
- monitoring
A fix has been fully implemented and we are monitoring the results.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
This incident has 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-3457159fbf
Is Sanity still down?
No, this incident was resolved 2026-10-08 14:28 UTC. For Sanity's live state, see https://down.guide/providers/sanity.
How long did it last?
4h 34m, from 2026-10-08 09:55 UTC to 2026-10-08 14:28 UTC, by the times Sanity posted.
What was affected?
Sanity named Studio.
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.