Major impactResolvedCMS

Sanity outage: Slow Query Performance for Some Customers

Sanity reported this major-impact incident on its official status page on Jun 15, 2026, 06:15 UTC. It was resolved after 4h 9m.

Right now Sanity is operational. Live Sanity status →

🔔 Get alerted when Sanity has issuesFree · email alerts · no credit card
Jun 15, 2026, 06:15 UTC
started
Jun 15, 2026, 10:24 UTC
resolved
4h 9m
duration
Major
impact

Affected components

  • GraphQL
  • api.sanity.io
  • apicdn.sanity.io
  1. resolvedJun 15, 2026, 10:24 UTC

    This incident has been resolved.

  2. monitoringJun 15, 2026, 08:30 UTC

    A fix has been implemented and we are monitoring the results.

  3. identifiedJun 15, 2026, 07:00 UTC

    The issue has been identified and a fix is being implemented.

  4. investigatingJun 15, 2026, 06:15 UTC

    We are currently investigating an issue causing slower-than-expected query performance for some customers. A subset of users may experience increased latency when querying content. Our team is actively investigating the issue and working to mitigate the impact. We will provide further updates as more information becomes 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

Sanity outage on Jun 15, 2026: Slow Query Performance for Some Customers · APIStatus.watch