Skip to main content
Sanity

Installation issues affecting the Sanity package

Partial outage Lasted 58m · started · Sanity's page

Level
confirmed
Worst impact
Partial outage
Components
Studio
Down Index
28of 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 58m it lasted.

    Anything that failed between 2026-02-18 18:45 UTC and 2026-02-18 19:43 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 3

  1. identified

    We’re investigating an issue where Sanity may fail to install due to a third-party dependency. We’ve identified the cause and have reached out to the dependency maintainer. We’ll share an update as soon as more information is available.

    provider

  2. monitoring

    The dependency maintainer has implemented a fix, and we are currently monitoring the results.

    provider

  3. 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-0819fba777

Is Sanity still down?

No, this incident was resolved 2026-02-18 19:43 UTC. For Sanity's live state, see https://down.guide/sanity.

How long did it last?

58m, from 2026-02-18 18:45 UTC to 2026-02-18 19:43 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.