Sanity

Affected: api.sanity.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-20 15:54 UTC

   Between 14:56 and 15:16 UTC, we observed a slight increase in 524 error rates for a small subset of customers. The error rates have returned to normal, though we continue to investigate the cause.

2. monitoring 2026-10-20 16:25 UTC

   A fix has been implemented to mitigate the cause of these elevated API errors in the future. We are monitoring its rollout.

3. resolved 2026-10-20 18:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-14 12:48 UTC

   We are investigating intermittent increased latency affecting API requests for a small subset of customers. Some requests may also have returned errors. Most customers are unaffected. Our engineers have identified the cause and have taken steps to reduce the impact while we...

2. monitoring 2026-10-14 13:44 UTC

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

3. resolved 2026-10-15 10:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Functions, Studio, Dataset Embeddings

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-08 17:49 UTC

   We are investigating an issue of elevated listener latency, which may cause performance issues in the Studio for some customers.

2. investigating 2026-10-08 18:27 UTC

   We are investigating an issue of elevated listener latency, which may cause performance issues in the Studio for some customers. Dataset embeddings may be stale at this time.

3. investigating 2026-10-08 18:57 UTC

   We are investigating an issue of elevated listener latency, which may cause performance issues in the Studio for some customers. Dataset embeddings may be stale at this time. The triggering of Functions may be delayed or time out.

4. identified 2026-10-08 19:24 UTC

   The triggering of Functions and listener performance have returned to normal. Dataset embeddings may continue to be stale for some customers.

5. monitoring 2026-10-08 20:08 UTC

   A fix has been fully implemented, and we are monitoring results. Some users may see stale Dataset Embeddings while processing catches up.

6. resolved 2026-10-09 07:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Studio

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-08 09:55 UTC

   We are currently investigating an issue where elevated listener latency may result in slower performance and lag within Sanity Studio for a subset of customers. Our team is actively working to identify the root cause and mitigate the impact. Issue starting around 9:10 UTC.

2. investigating 2026-10-08 10:10 UTC

   We are continuing to investigate this issue.

3. investigating 2026-10-08 10:27 UTC

   We are currently continuing to investigate the issue, while also rolling out mitigations.

4. investigating 2026-10-08 10:37 UTC

   We are continuing to investigate the issue. Additionally, there might be a slight delay in document publishes for "scheduled publishing" functionality.

5. investigating 2026-10-08 10:56 UTC

   We are currently continuing to investigate the issue, while also preparing to roll a set of mitigations.

6. investigating 2026-10-08 11:01 UTC

   We are continuing to investigate this issue.

7. investigating 2026-10-08 11:21 UTC

   We are continuing to investigate this issue.

8. investigating 2026-10-08 11:38 UTC

   We're continuing to investigate this issue. In the meantime, we've begun rolling out preliminary measures to mitigate its impact.

9. investigating 2026-10-08 11:58 UTC

   We're continuing to investigate this issue. And we are continuing rolling out preliminary measures to mitigate its impact.

10. investigating 2026-10-08 12:18 UTC

    We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact. "scheduled publishing" functionality confirmed unaffected by this incident.

11. investigating 2026-10-08 12:33 UTC

    We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact.

12. investigating 2026-10-08 12:50 UTC

    We're continuing to investigate this issue. And we are continuing to apply measures to mitigate its impact.

13. identified 2026-10-08 13:13 UTC

    The issue has been identified. We are continuing to apply fixes to mitigate its impact.

14. identified 2026-10-08 13:32 UTC

    We are continuing to apply fixes to mitigate the impact.

15. identified 2026-10-08 13:46 UTC

    We are continuing to apply fixes to mitigate the impact. No errors have been observed from the changes rolled out so far.

16. monitoring 2026-10-08 13:57 UTC

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

17. monitoring 2026-10-08 14:13 UTC

    We are continuing to monitor for any further issues.

18. resolved 2026-10-08 14:28 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Content Agent

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 10:54 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 2026-09-23 10:57 UTC

   We are continuing to investigate this issue.

3. investigating 2026-09-23 11:12 UTC

   We are continuing to investigate this issue.

4. monitoring 2026-09-23 11:23 UTC

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

5. monitoring 2026-09-23 11:38 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-09-23 11:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Studio

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-22 08:27 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 starting around 7:40 UTC....

2. investigating 2026-09-22 08:45 UTC

   We are currently continuing to investigate the issue.

3. investigating 2026-09-22 09:05 UTC

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

4. investigating 2026-09-22 09:15 UTC

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

5. monitoring 2026-09-22 09:33 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 2026-09-22 10:02 UTC

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

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io, Studio

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-15 11:46 UTC

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

2. investigating 2026-09-15 11:48 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...

3. investigating 2026-09-15 11:48 UTC

   We are continuing to investigate this issue.

4. identified 2026-09-15 12:12 UTC

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

5. monitoring 2026-09-15 12:15 UTC

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

6. resolved 2026-09-15 12:21 UTC

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

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Manage

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-01 07:31 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...

2. monitoring 2026-09-01 07:35 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 2026-09-01 07:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-27 04:30 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.

Excerpts are shortened. Read the full incident on Sanity's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-26 08:00 UTC

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

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io, apicdn.sanity.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-20 14:33 UTC

   Starting at approximately 13:05–13:45 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.

Excerpts are shortened. Read the full incident on Sanity's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-17 07:45 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.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io, apicdn.sanity.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-14 14:46 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 2026-08-14 14:53 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 2026-08-14 15:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-06 09:45 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.

Excerpts are shortened. Read the full incident on Sanity's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-24 23:16 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...

Excerpts are shortened. Read the full incident on Sanity's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-07-22 21:30 UTC

   Between 18:00 and 21:00 UTC, we experienced partial outages on the Live Content API in some regions. The incident is now resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-22 11:45 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...

2. monitoring 2026-07-22 12:01 UTC

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

3. investigating 2026-07-22 12:38 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...

4. monitoring 2026-07-22 13:04 UTC

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

5. identified 2026-07-22 13:04 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 2026-07-22 14:12 UTC

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

7. monitoring 2026-07-22 15:37 UTC

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

8. resolved 2026-07-22 18:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Webhooks

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-21 16:32 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 2026-07-21 18:11 UTC

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

3. resolved 2026-07-21 19:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-06-25 20:30 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.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io, apicdn.sanity.io, GraphQL

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-15 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...

2. identified 2026-06-15 07:00 UTC

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

3. monitoring 2026-06-15 08:30 UTC

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

4. resolved 2026-06-15 10:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Content Agent

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-29 09:19 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 2026-05-29 09:21 UTC

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

3. monitoring 2026-05-29 10:03 UTC

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

4. resolved 2026-05-29 15:14 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: MCP Server

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-01 12:00 UTC

   Our MCP server (mcp.sanity.io) is currently inoperative, returning 500 errors and impacting access via tools like Claude and Cursor. We are working to restore functionality.

2. identified 2026-05-01 12:46 UTC

   We are implementing a fix that should resolve the issue.

3. identified 2026-05-01 12:48 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 2026-05-01 12:49 UTC

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

5. identified 2026-05-01 13:08 UTC

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

6. monitoring 2026-05-01 13:11 UTC

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

7. resolved 2026-05-01 13:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io, Manage

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-04-14 07:49 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.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Studio

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-04-13 07:45 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.

Excerpts are shortened. Read the full incident on Sanity's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-04-06 14:00 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.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Studio

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-03 13:38 UTC

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

2. monitoring 2026-04-03 14:37 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 2026-04-03 19:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: cdn.sanity.io

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-22 13:58 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 2026-03-22 14:23 UTC

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

3. monitoring 2026-03-22 14:48 UTC

   A fix has been implemented and we are monitoring results.

4. resolved 2026-03-22 16:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-03-21 11:30 UTC

   Between 10:12 and 11:08 UTC, we experienced a sustained error rate on the Asset CDN. Some customers will have received elevated rates of 5xx errors when requesting images during this time. A fix was implemented at 11:03 UTC and the Asset CDN fully recovered by 11:08 UTC. We...

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Authentication

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-12 12:11 UTC

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

2. investigating 2026-03-12 12:29 UTC

   We are continuing to investigate this issue.

3. investigating 2026-03-12 12:49 UTC

   We are continuing to investigate this issue.

4. investigating 2026-03-12 13:14 UTC

   We are continuing to investigate this issue.

5. identified 2026-03-12 13:19 UTC

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

6. monitoring 2026-03-12 13:22 UTC

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

7. resolved 2026-03-12 13:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: www.sanity.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-06 18:39 UTC

   Our sales contact form on www.sanity.io is currently inoperative. We are working to restore functionality.

2. resolved 2026-03-06 18:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-03-02 23:10 UTC

   Resolved: Between 16:00–23:10 UTC, a subset of customers experienced elevated API CDN latency. The issue has been mitigated and performance is back to normal.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Media Library, Asset Pipeline, Studio

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-24 11:07 UTC

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

2. monitoring 2026-02-24 11:24 UTC

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

3. monitoring 2026-02-24 11:45 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-02-24 12:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io, Studio

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-24 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...

2. monitoring 2026-02-24 10:29 UTC

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

3. monitoring 2026-02-24 11:11 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2026-02-24 13:14 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-02-24 15:58 UTC

   The incident has been resolved

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io, apicdn.sanity.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-19 19:53 UTC

   We are currently investigating an increase in API and API CDN errors and latency impacting a subset of customers. We are actively mitigating the impact while working to identify the issue.

2. monitoring 2026-02-19 20:19 UTC

   We've identified and mitigated the issue. Performance has been stable since 19:46 UTC with no elevated error rates, and we are continuing to monitor.

3. resolved 2026-02-19 20:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Studio

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-02-18 18:45 UTC

   We’re investigating an issue where Sanity may fail to install due to a third-party dependency. We’ve identified the cause and have reached out to the dependency maintainer. We’ll share an update as soon as more information is available.

2. monitoring 2026-02-18 19:22 UTC

   The dependency maintainer has implemented a fix, and we are currently monitoring the results.

3. resolved 2026-02-18 19:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Dataset Management

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-09 13:50 UTC

   We are mitigating an issue causing inconsistencies in data returned from the History API for a subset of customers. This issue started on February 5th 2026 for the datasets created after December 9th 2025 and not mutated since until 26th January 2026, this also impacts the...

2. identified 2026-02-09 14:34 UTC

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

3. identified 2026-02-09 15:12 UTC

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

4. identified 2026-02-09 15:54 UTC

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

5. monitoring 2026-02-09 16:21 UTC

   The underlying cause of the issue has been resolved. We are continuing internal monitoring and completing remediation for a small number of affected customer datasets, working directly with impacted customers as needed.

6. resolved 2026-02-10 13:39 UTC

   The issue has been resolved. All affected customer datasets have been remediated and the service is operating normally.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Content Agent, Canvas

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-04 10:23 UTC

   We’re investigating elevated error rates impacting Content Agent and Canvas functionality. Some requests may fail, though retries may sometimes succeed. We’re monitoring the upstream AI provider and will share updates as we have more information.

2. monitoring 2026-02-04 10:42 UTC

   A fix in our upstream AI provider has been implemented and we are monitoring the results.

3. resolved 2026-02-04 11:17 UTC

   This incident is resolved. Our upstream AI provider has recovered and Content Agent and Canvas error rates have returned to normal.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io, apicdn.sanity.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-03 16:06 UTC

   We are currently investigating an increase in API and API CDN errors and latency impacting a subset of customers. We are actively mitigating impact while working to identify the issue.

2. monitoring 2026-02-03 16:34 UTC

   We've identified and mitigated the root cause of the issue. Performance has been stable since 16:17 UTC with no elevated error rates, and we are continuing to monitor.

3. resolved 2026-02-03 21:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Content Agent, Canvas

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-03 15:54 UTC

   We’re investigating elevated error rates impacting Content Agent and Canvas functionality. Some requests may fail, though retries may sometimes succeed. We’re monitoring the upstream AI provider and will share updates as we have more information.

2. identified 2026-02-03 15:57 UTC

   The issue in our upstream AI provider has been identified and a fix is being implemented.

3. resolved 2026-02-03 16:08 UTC

   A fix has been implemented at provider level. This incident is resolved. Our upstream AI provider has recovered and Content Agent and Canvas error rates have returned to normal.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Content Agent, Canvas

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-21 14:53 UTC

   We’re investigating elevated error rates impacting Content Agent and Canvas functionality. Some requests may fail, though retries may sometimes succeed. We’re monitoring the upstream AI provider and will share updates as we have more information.

2. investigating 2026-01-21 14:59 UTC

   We are continuing to investigate this issue.

3. investigating 2026-01-21 15:00 UTC

   We are continuing to investigate this issue.

4. identified 2026-01-21 15:06 UTC

   The issue in our upstream AI provider has been identified and a fix is being implemented.

5. monitoring 2026-01-21 15:31 UTC

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

6. resolved 2026-01-21 15:33 UTC

   This incident is resolved. Our upstream AI provider has recovered and Content Agent and Canvas error rates have returned to normal.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Content Agent, Canvas

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-20 17:32 UTC

   We’re investigating elevated error rates impacting Content Agent and Canvas. Some requests may fail with 5xx errors, though retries may sometimes succeed. We’re monitoring the upstream AI provider and will share updates as we learn more.

2. resolved 2026-01-20 17:58 UTC

   This incident is resolved. Our upstream AI provider has recovered, and Content Agent and Canvas error rates have returned to normal.

Excerpts are shortened. Read the full incident on Sanity's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-01-20 09:00 UTC

   On January 20th at 8:52pm UTC, there was an update to the Sanity CLI that had a regression when trying to run the init flow (`npm create sanity@latest`) that resulted in a non-functioning project. This update was rolled back at January 21st at ~2am UTC. As of January 21st, the...

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io, apicdn.sanity.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-20 08:19 UTC

   We are currently investigating an increase in API and API CDN errors and latency impacting a subset of customers. We are actively mitigating impact while working to identify the issue.

2. investigating 2026-01-20 08:20 UTC

   We are continuing to investigate this issue.

3. investigating 2026-01-20 08:34 UTC

   We are continuing to investigate this issue. And making adjustments in our internal systems.

4. monitoring 2026-01-20 08:44 UTC

   We've identified and mitigated root cause of the issue. Performance has been stable since 8:36 UTC (start of degraded performance at 7:52 UTC) with no elevated error rates.

5. resolved 2026-01-20 09:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io, apicdn.sanity.io

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-15 12:23 UTC

   We are currently investigating an increase in API and API CDN errors and latency impacting a subset of customers. We are actively mitigating impact while working to identify the issue.

2. monitoring 2026-01-15 12:42 UTC

   Mitigations have been applied and error rates have returned to normal. Customers who were seeing intermittent timeouts/errors on write operations and document retrieval should see recovery. We continue monitoring results to ensure stability.

3. resolved 2026-01-15 13:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Dashboard

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-14 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.

2. resolved 2026-01-14 11:34 UTC

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

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Content Agent, Canvas

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-14 10:24 UTC

   We’re investigating elevated error rates impacting Content Agent and Canvas. Some requests may fail with 5xx errors, though retries may sometimes succeed. We’re monitoring the upstream AI provider and will share updates as we learn more.

2. investigating 2026-01-14 11:00 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-01-14 11:15 UTC

   We’re monitoring an incident with our upstream AI provider impacting Content Agent and Canvas. We’ll share updates as we receive further information from the provider.

4. monitoring 2026-01-14 12:02 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-01-14 14:17 UTC

   This incident is resolved. Our upstream AI provider has recovered and Content Agent and Canvas error rates have returned to normal.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: apicdn.sanity.io

Failure mode: CDN or edge layer failed or served bad content. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-05 14:05 UTC

   Beginning around 13:40 UTC we began experiencing elevated error rates on our API CDN in certain regions. As a result, some requests may respond with a 5xx status. We're investigating the issue now.

2. monitoring 2026-01-05 14:26 UTC

   We've mitigated the original issue and are no longer seeing elevated error rates. We're continuing to monitor and while we investigate the root cause.

3. resolved 2026-01-05 14:43 UTC

   The issue was related to a higher than expected load which has been resolved. All operations are back to normal and we'll continue to monitor our systems closely.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-18 11:15 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...

2. monitoring 2025-12-18 12:41 UTC

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

3. resolved 2025-12-18 13:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: api.sanity.io, apicdn.sanity.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-09 08:50 UTC

   We are currently investigating query slowdowns and 503 responses for a small subset of customers, starting at 08:32 UTC. We are actively mitigating impact while working to identify the issue.

2. monitoring 2025-12-09 09:05 UTC

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

3. resolved 2025-12-09 09:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.

Affected: Partner Integrations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-08 09:50 UTC

   We are aware of an issue with setting up new Vercel integrations with Sanity. We have identified the cause and are working on restoring service. This does not affect existing integrations

2. monitoring 2025-12-08 10:16 UTC

   Our team has applied the required updates, and are awaiting further guidance from Vercel.

3. monitoring 2025-12-08 18:57 UTC

   Updates have been applied and confirmed by Vercel. This incident has been resolved.

4. resolved 2025-12-08 18:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sanity's status page.