Minor impactResolvedCMS

Sanity incident: Content Releases & Scheduled Drafts - Sameorigin error when accessing via Dashboard

Sanity reported this minor-impact incident on its official status page on Jan 14, 2026, 10:48 UTC. It was resolved after 47 min.

Right now Sanity is operational. Live Sanity status →

🔔 Get alerted when Sanity has issuesFree · email alerts · no credit card
Jan 14, 2026, 10:48 UTC
started
Jan 14, 2026, 11:34 UTC
resolved
47 min
duration
Minor
impact

Affected components

  • Dashboard

Timeline

updates from Sanity's status page ↗
  1. resolvedJan 14, 2026, 11:34 UTC

    This issue has now been resolved. A fix has been implemented and deployed with Sanity Studio version 5.3.1.

  2. investigatingJan 14, 2026, 10:48 UTC

    We have identified that some users may experience sameorigin errors when attempting to access Content Releases and Scheduled Drafts when accessing a Sanity Studio on versions 5.2.0 or 5.3.0 via the Dashboard. We are currently investigating, and implementing a short-term fix.

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: Content Agent & Canvas experiencing elevated error rates (Jan 14, 2026)Next: Elevated API and API CDN errors and latency for some customers (Jan 15, 2026) →
Sanity incident on Jan 14, 2026: Content Releases & Scheduled Drafts - Sameorigin error when accessing via Dashboard · APIStatus.watch