Major impactResolvedCMS

Sanity outage: Installation issues affecting the Sanity package

Sanity reported this major-impact incident on its official status page on Feb 18, 2026, 18:45 UTC. It was resolved after 58 min.

Right now Sanity is operational. Live Sanity status →

🔔 Get alerted when Sanity has issuesFree · email alerts · no credit card
Feb 18, 2026, 18:45 UTC
started
Feb 18, 2026, 19:43 UTC
resolved
58 min
duration
Major
impact

Affected components

  • Studio

Timeline

updates from Sanity's status page ↗
  1. resolvedFeb 18, 2026, 19:43 UTC

    This incident has been resolved.

  2. monitoringFeb 18, 2026, 19:22 UTC

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

  3. identifiedFeb 18, 2026, 18:45 UTC

    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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Sanity's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Sanity have incidents?

Sanity reported 10 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 52 min. See Sanity's uptime and incident history

← Previous: History API inconsistencies (Feb 9, 2026)Next: Elevated API and API CDN errors and latency for some customers (Feb 19, 2026) →
Sanity outage on Feb 18, 2026: Installation issues affecting the Sanity package · APIStatus.watch