Sanity incident: Elevated listener latency impacting Studio performance

Affected components

• Studio
• api.sanity.io

1. resolvedFeb 24, 2026, 15:58 UTC

   The incident has been resolved

2. monitoringFeb 24, 2026, 13:14 UTC

   We are continuing to monitor for any further issues.

3. monitoringFeb 24, 2026, 11:11 UTC

   We are continuing to monitor for any further issues.

4. monitoringFeb 24, 2026, 10:29 UTC

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

5. investigatingFeb 24, 2026, 09:56 UTC

   We are currently investigating an issue where elevated listener latency may result in slower performance and lag within Sanity Studio for some customers. Our team is actively working to identify the root cause and mitigate the impact. We’ll 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.

• PlanetScale: Vitess branch creation unavailableMajor · Feb 24, 2026, 10:26 UTC
• Confluent Cloud: Elevated Kafka Latency in GCP asia-southeast1Minor · Feb 23, 2026, 22:12 UTC

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