Sanity Outage History

Sanity is up right now

Sanity had 46 outages in the last 2 years totaling 34h 30m of downtime — averaging 1.9 incidents per month.

There were 46 Sanity outages since October 14, 2025 totaling 34h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.sanity.io

Major September 23, 2026

Content Agent - Elevated error rates

Detected by Pingoru
Sep 23, 2026, 10:54 AM UTC
Resolved
Sep 23, 2026, 11:53 AM UTC
Duration
59m
Affected: Content Agent
Timeline · 6 updates
  1. investigating Sep 23, 2026, 10:54 AM UTC

    We are aware of an issue with the Content Agent where responses are not being delivered back to the user. We are investigating and will provide an update shortly.

  2. investigating Sep 23, 2026, 10:57 AM UTC

    We are continuing to investigate this issue.

  3. investigating Sep 23, 2026, 11:12 AM UTC

    We are continuing to investigate this issue.

  4. monitoring Sep 23, 2026, 11:23 AM UTC

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

  5. monitoring Sep 23, 2026, 11:38 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Sep 23, 2026, 11:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 22, 2026

Elevated listener latency impacting Studio performance

Detected by Pingoru
Sep 22, 2026, 08:27 AM UTC
Resolved
Sep 22, 2026, 10:02 AM UTC
Duration
1h 35m
Affected: Studio
Timeline · 6 updates
  1. investigating Sep 22, 2026, 08:27 AM UTC

    We are currently investigating an issue where elevated listener latency may result in slower performance and lag within Sanity Studio for a small subset of customers. Our team is actively working to identify the root cause and mitigate the impact. Issue started around 7:40 UTC. We’ll provide further updates as more information becomes available.

  2. investigating Sep 22, 2026, 08:45 AM UTC

    We are currently continuing to investigate the issue.

  3. investigating Sep 22, 2026, 09:05 AM UTC

    The issue should not affect the performance of any Studios anymore. We are continuing to investigate the issue.

  4. investigating Sep 22, 2026, 09:15 AM UTC

    We have had another occurrence of listener latency. We are continuing to investigate the issue.

  5. monitoring Sep 22, 2026, 09:33 AM UTC

    We have identified the core issue and planning to roll out a set of updates to mitigate the problem. Studio performance should not be affected anymore. We are monitoring the incident now.

  6. resolved Sep 22, 2026, 10:02 AM UTC

    The incident has been resolved. Further optimization work is planned as part of a broader effort.

Read the full incident report →

Minor September 15, 2026

Elevated API Errors

Detected by Pingoru
Sep 15, 2026, 11:46 AM UTC
Resolved
Sep 15, 2026, 12:21 PM UTC
Duration
34m
Affected: api.sanity.ioStudio
Timeline · 6 updates
  1. investigating Sep 15, 2026, 11:46 AM UTC

    Some of our users may be experiencing an elevated level of API errors. We are currently looking into the issue.

  2. investigating Sep 15, 2026, 11:48 AM UTC

    We are investigating elevated error rates affecting write requests (mutations) for a subset of projects, starting at approximately 11:20 UTC today. Affected users may see intermittent errors or slower response times when creating, updating, or publishing documents, including from Sanity Studio.

  3. investigating Sep 15, 2026, 11:48 AM UTC

    We are continuing to investigate this issue.

  4. identified Sep 15, 2026, 12:12 PM UTC

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

  5. monitoring Sep 15, 2026, 12:15 PM UTC

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

  6. resolved Sep 15, 2026, 12:21 PM UTC

    This incident has been resolved. Error rates have returned to normal.

Read the full incident report →

Minor September 1, 2026

Payment form not loading in Manage

Detected by Pingoru
Sep 01, 2026, 07:31 AM UTC
Resolved
Sep 01, 2026, 07:46 AM UTC
Duration
15m
Affected: Manage
Timeline · 3 updates
  1. identified Sep 01, 2026, 07:31 AM UTC

    We've identified an issue preventing the payment form from loading in Manage. Customers without a saved card are currently unable to add a payment method or upgrade their plan. Existing subscriptions and saved payment methods are not affected. The cause has been identified and a fix is being deployed. We'll post an update once it's live.

  2. monitoring Sep 01, 2026, 07:35 AM UTC

    The fix has been deployed and the payment form is restored. We're verifying the affected flows and monitoring for any further issues.

  3. resolved Sep 01, 2026, 07:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 27, 2026

Elevated Embedding Index Error Rates

Detected by Pingoru
Aug 27, 2026, 04:30 AM UTC
Resolved
Aug 27, 2026, 04:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 27, 2026, 07:59 AM UTC

    Starting at approximating 6:33 UTC , we saw elevated error rates (HTTP 5xx) on requests to the Embeddings Index service. The issue was identified and resolved at roughly 7:16 UTC.

Read the full incident report →

Minor August 26, 2026

Elevated Embedding Index and Agentic flows Error Rates

Detected by Pingoru
Aug 26, 2026, 08:00 AM UTC
Resolved
Aug 26, 2026, 08:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 26, 2026, 09:14 PM UTC

    Starting at approximating 19:51 UTC, we saw elevated error rates (HTTP 5xx) on requests to the Embeddings Index service. The issue was identified and resolved at roughly 20:32 UTC.

Read the full incident report →

Notice August 20, 2026

Elevated API error rate

Detected by Pingoru
Aug 20, 2026, 02:33 PM UTC
Resolved
Aug 20, 2026, 02:33 PM UTC
Duration
—
Affected: api.sanity.ioapicdn.sanity.io
Timeline · 1 update
  1. resolved Aug 20, 2026, 02:33 PM UTC

    Starting at approximately 13:25–13:30 UTC, we saw elevated API error rates for a small subset of customers due to intermittent timeouts on API requests. The issue has been identified and resolved.

Read the full incident report →

Notice August 17, 2026

Intermittent Studio connectivity issues for some customers

Detected by Pingoru
Aug 17, 2026, 07:45 AM UTC
Resolved
Aug 17, 2026, 07:45 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 17, 2026, 08:54 AM UTC

    Some customers experienced intermittent Studio connectivity issues between approximately 07:25 and 07:45 UTC on August 17. The issue has been resolved and services have returned to normal operation.

Read the full incident report →

Major August 14, 2026

Elevated API and API CDN rates

Detected by Pingoru
Aug 14, 2026, 02:46 PM UTC
Resolved
Aug 14, 2026, 03:32 PM UTC
Duration
45m
Affected: api.sanity.ioapicdn.sanity.io
Timeline · 3 updates
  1. investigating Aug 14, 2026, 02:46 PM UTC

    Starting at approximately 14:30 UTC, we have seen elevated API and API CDN error rates. We are currently investigating the issue.

  2. monitoring Aug 14, 2026, 02:53 PM UTC

    A fix was implemented and service rates returned to normal at 14:40 UTC. The period of elevated error rates was identified to have started at 14:34 UTC. We are continuing to monitor.

  3. resolved Aug 14, 2026, 03:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 6, 2026

Elevated API and API CDN error rate for some customers

Detected by Pingoru
Aug 06, 2026, 09:45 AM UTC
Resolved
Aug 06, 2026, 09:45 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 06, 2026, 12:46 PM UTC

    Between approximately 09:25 and 09:45 UTC on August 6, some requests to api.sanity.io and apicdn.sanity.io returned errors or timed out for a small subset of customers. The issue has been resolved and API services have returned to normal operation.

Read the full incident report →

Notice July 24, 2026

Elevated errors serving images and assets

Detected by Pingoru
Jul 24, 2026, 11:16 PM UTC
Resolved
Jul 24, 2026, 11:16 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 25, 2026, 12:37 AM UTC

    Between approximately 23:16 UTC on July 24 and 00:10 UTC on July 25, some requests for images and assets served from cdn.sanity.io returned errors or loaded slowly for users in North America and Europe. Image and asset delivery has since returned to normal operation. The Content APIs (api.sanity.io, apicdn.sanity.io) and Studio editing were not affected.

Read the full incident report →

Major July 22, 2026

Studio Connectivity Issues

Detected by Pingoru
Jul 22, 2026, 12:38 PM UTC
Resolved
Jul 22, 2026, 06:05 PM UTC
Duration
5h 27m
Affected: api.sanity.ioStudio
Timeline · 8 updates
  1. investigating Jul 22, 2026, 11:45 AM UTC

    We are investigating reports of connectivity issues affecting Sanity Studio. Some users may experience the Studio getting stuck on "Trying to connect" or failing to load. Our engineering team is actively investigating the issue and we will provide updates as soon as more information is available.

  2. monitoring Jul 22, 2026, 12:01 PM UTC

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

  3. investigating Jul 22, 2026, 01:22 PM UTC

    We have identified that the issue has recurred for some users after the earlier mitigation. Our engineering team is actively investigating the remaining connectivity issues and working to restore full service. We will continue to provide updates as more information becomes available.

  4. monitoring Jul 22, 2026, 01:23 PM UTC

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

  5. identified Jul 22, 2026, 03:11 PM UTC

    We've identified a recurrence of the issue affecting additional services. Our engineering team is actively implementing further mitigation and investigating the remaining impact. We will continue to provide updates as they become available.

  6. identified Jul 22, 2026, 03:52 PM UTC

    We are continuing to work on a fix for this issue.

  7. monitoring Jul 22, 2026, 03:53 PM UTC

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

  8. resolved Jul 22, 2026, 06:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 21, 2026

Issue Viewing Webhooks

Detected by Pingoru
Jul 21, 2026, 04:32 PM UTC
Resolved
Jul 21, 2026, 07:22 PM UTC
Duration
2h 49m
Affected: Webhooks
Timeline · 3 updates
  1. investigating Jul 21, 2026, 04:32 PM UTC

    We're currently investigating an issue where the Webhooks page fails to load webhook data. This does not affect webhook delivery. Webhooks configured on your project will continue to fire as expected.

  2. monitoring Jul 21, 2026, 06:11 PM UTC

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

  3. resolved Jul 21, 2026, 07:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 25, 2026

Query Performance Degradation for Some Customers

Detected by Pingoru
Jun 25, 2026, 08:30 PM UTC
Resolved
Jun 25, 2026, 08:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 26, 2026, 09:53 AM UTC

    A small subset of customers experienced increased query latency and intermittent timeouts during this incident. Our engineering team identified the issue, implemented mitigations, and restored normal query performance. The incident has been resolved.

Read the full incident report →

Major June 15, 2026

Slow Query Performance for Some Customers

Detected by Pingoru
Jun 15, 2026, 06:15 AM UTC
Resolved
Jun 15, 2026, 10:24 AM UTC
Duration
4h 9m
Affected: api.sanity.ioapicdn.sanity.ioGraphQL
Timeline · 4 updates
  1. investigating Jun 15, 2026, 08:49 AM 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.

  2. identified Jun 15, 2026, 08:50 AM UTC

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

  3. monitoring Jun 15, 2026, 08:51 AM UTC

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

  4. resolved Jun 15, 2026, 10:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 29, 2026

Content Agent - Delivery issue with some longer-running threads

Detected by Pingoru
May 29, 2026, 09:19 AM UTC
Resolved
May 29, 2026, 03:14 PM UTC
Duration
5h 55m
Affected: Content Agent
Timeline · 4 updates
  1. investigating May 29, 2026, 09:19 AM UTC

    We are aware of an issue with the Content Agent in Dashboard where a small number of responses in longer-running threads may not be delivered to the user. We are investigating and will provide an update shortly.

  2. identified May 29, 2026, 09:21 AM UTC

    The issue has been identified and we are working on a fix.

  3. monitoring May 29, 2026, 10:03 AM UTC

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

  4. resolved May 29, 2026, 03:14 PM UTC

    This incident has now been resolved.

Read the full incident report →

Major May 1, 2026

MCP server returning 500 errors

Detected by Pingoru
May 01, 2026, 12:34 PM UTC
Resolved
May 01, 2026, 12:45 PM UTC
Duration
10m
Affected: Partner Integrations
Timeline · 1 update
  1. investigating May 01, 2026, 12:34 PM UTC

    We’re investigating an issue with the MCP server (mcp.sanity.io) returning 500 errors. This may impact access via tools like Claude, Cursor, and other MCP-compatible clients. Updates to follow.

Read the full incident report →

Major May 1, 2026

Sanity MCP Server Unavailability

Detected by Pingoru
May 01, 2026, 12:00 PM UTC
Resolved
May 01, 2026, 01:19 PM UTC
Duration
1h 18m
Affected: Partner IntegrationsMCP Server
Timeline · 7 updates
  1. investigating May 01, 2026, 12:34 PM UTC

    Our MCP server is currently inoperative. We are working to restore functionality.

  2. identified May 01, 2026, 12:46 PM UTC

    We are implementing a fix that should resolve the issue.

  3. identified May 01, 2026, 12:48 PM UTC

    We’ve identified the issue affecting the MCP server (mcp.sanity.io) and are actively working on a fix. We’ll share another update as soon as we have more information.

  4. identified May 01, 2026, 12:49 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified May 01, 2026, 01:08 PM UTC

    We are continuing to work on a fix for this issue.

  6. monitoring May 01, 2026, 01:11 PM UTC

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

  7. resolved May 01, 2026, 01:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 14, 2026

Issues with organization and project creation

Detected by Pingoru
Apr 14, 2026, 07:48 AM UTC
Resolved
Apr 14, 2026, 07:49 AM UTC
Duration
—
Affected: api.sanity.ioManage
Timeline · 1 update
  1. resolved Apr 14, 2026, 07:49 AM UTC

    Between 06:01 and 06:35 UTC today, some users encountered errors when attempting to create organizations, create projects, or make plan changes. This was caused by an internal service configuration issue that has since been rolled back.

Read the full incident report →

Notice April 13, 2026

Studio loading issues

Detected by Pingoru
Apr 13, 2026, 07:45 AM UTC
Resolved
Apr 13, 2026, 07:45 AM UTC
Duration
—
Affected: Studio
Timeline · 1 update
  1. resolved Apr 13, 2026, 07:45 AM UTC

    Between approximately 06:35 and 06:52 UTC today, some users may have experienced issues loading Sanity Studio. This was caused by a temporary service disruption in our infrastructure. The issue is resolved and a fix has been deployed to prevent recurrence.

Read the full incident report →

Minor April 6, 2026

Elevated API Error Rates

Detected by Pingoru
Apr 06, 2026, 02:00 PM UTC
Resolved
Apr 06, 2026, 02:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 06, 2026, 03:27 PM UTC

    Between 14:14 UTC and 14:20 UTC, we observed elevated error rates on our API for some customers. The issue has since been resolved and all systems are operating normally.

Read the full incident report →

Minor April 3, 2026

Issues with Loading Document Lists in Sanity Studio

Detected by Pingoru
Apr 03, 2026, 01:38 PM UTC
Resolved
Apr 03, 2026, 07:45 PM UTC
Duration
6h 6m
Affected: Studio
Timeline · 3 updates
  1. investigating Apr 03, 2026, 01:38 PM UTC

    We’re currently investigating an issue affecting Sanity Studio where some users may see documents and document lists fail to load.

  2. monitoring Apr 03, 2026, 02:37 PM UTC

    We’ve taken steps to address an issue affecting Sanity Studio where some users experienced documents and document lists failing to load, and are continuing to monitor the situation closely.

  3. resolved Apr 03, 2026, 07:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 22, 2026

Elevated error rates on the Asset CDN

Detected by Pingoru
Mar 22, 2026, 01:58 PM UTC
Resolved
Mar 22, 2026, 04:42 PM UTC
Duration
2h 43m
Affected: cdn.sanity.io
Timeline · 4 updates
  1. investigating Mar 22, 2026, 01:58 PM UTC

    Starting 12:47 UTC, we are experiencing a sustained error rate on the Asset CDN. Some customers will be seeing elevated rates of 5xx errors when requesting images during this time.

  2. identified Mar 22, 2026, 02:23 PM UTC

    The issue has been identified and we are working on a fix.

  3. monitoring Mar 22, 2026, 02:48 PM UTC

    A fix has been implemented and we are monitoring results.

  4. resolved Mar 22, 2026, 04:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 12, 2026

Issue with login via SSO/SAML

Detected by Pingoru
Mar 12, 2026, 12:11 PM UTC
Resolved
Mar 12, 2026, 01:49 PM UTC
Duration
1h 38m
Affected: Authentication
Timeline · 7 updates
  1. investigating Mar 12, 2026, 12:11 PM UTC

    We are currently investigating an issue with account logins via SAML SSO. This is not affecting the email/password login flow.

  2. investigating Mar 12, 2026, 12:29 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 12, 2026, 12:49 PM UTC

    We are continuing to investigate this issue.

  4. investigating Mar 12, 2026, 01:14 PM UTC

    We are continuing to investigate this issue.

  5. identified Mar 12, 2026, 01:19 PM UTC

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

  6. monitoring Mar 12, 2026, 01:22 PM UTC

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

  7. resolved Mar 12, 2026, 01:49 PM UTC

    This incident has been resolved.

Read the full incident report →