Minor impactResolvedCMS

Sanity incident: Elevated error rates with asset upload

Sanity reported this minor-impact incident on its official status page on Feb 24, 2026, 11:07 UTC. It was resolved after 59 min.

Right now Sanity is operational. Live Sanity status →

🔔 Get alerted when Sanity has issuesFree · email alerts · no credit card
Feb 24, 2026, 11:07 UTC
started
Feb 24, 2026, 12:06 UTC
resolved
59 min
duration
Minor
impact

Affected components

  • Asset Pipeline
  • Media Library
  • Studio

Timeline

updates from Sanity's status page ↗
  1. resolvedFeb 24, 2026, 12:06 UTC

    This incident has been resolved.

  2. monitoringFeb 24, 2026, 11:45 UTC

    We are continuing to monitor for any further issues.

  3. monitoringFeb 24, 2026, 11:24 UTC

    We can see that error levels have returned to normal, and are continuing to monitor.

  4. investigatingFeb 24, 2026, 11:07 UTC

    We are aware of elevated errors with the uploading of assets for some customers, and are currently investigating.

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: Elevated listener latency impacting Studio performance (Feb 24, 2026)Next: Issue with login via SSO/SAML (Mar 12, 2026) →
Sanity incident on Feb 24, 2026: Elevated error rates with asset upload · APIStatus.watch