- 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
-
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.
-
identified Jun 15, 2026, 08:50 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 15, 2026, 08:51 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 15, 2026, 10:39 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
identified May 29, 2026, 09:21 AM UTC
The issue has been identified and we are working on a fix.
-
monitoring May 29, 2026, 10:03 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 29, 2026, 03:14 PM UTC
This incident has now been resolved.
Read the full incident report →
- 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
-
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 →
- 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
-
investigating May 01, 2026, 12:34 PM UTC
Our MCP server is currently inoperative. We are working to restore functionality.
-
identified May 01, 2026, 12:46 PM UTC
We are implementing a fix that should resolve the issue.
-
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.
-
identified May 01, 2026, 12:49 PM UTC
We are continuing to work on a fix for this issue.
-
identified May 01, 2026, 01:08 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring May 01, 2026, 01:11 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 01, 2026, 01:19 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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 →
- Detected by Pingoru
- Apr 13, 2026, 07:45 AM UTC
- Resolved
- Apr 13, 2026, 07:45 AM UTC
- Duration
- —
Affected: Studio
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Apr 06, 2026, 03:27 PM UTC
- Resolved
- Apr 06, 2026, 02:00 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- 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
-
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.
-
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.
-
resolved Apr 03, 2026, 07:45 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
identified Mar 22, 2026, 02:23 PM UTC
The issue has been identified and we are working on a fix.
-
monitoring Mar 22, 2026, 02:48 PM UTC
A fix has been implemented and we are monitoring results.
-
resolved Mar 22, 2026, 04:42 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
investigating Mar 12, 2026, 12:29 PM UTC
We are continuing to investigate this issue.
-
investigating Mar 12, 2026, 12:49 PM UTC
We are continuing to investigate this issue.
-
investigating Mar 12, 2026, 01:14 PM UTC
We are continuing to investigate this issue.
-
identified Mar 12, 2026, 01:19 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 12, 2026, 01:22 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 12, 2026, 01:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 06:39 PM UTC
- Resolved
- Mar 06, 2026, 06:55 PM UTC
- Duration
- 16m
Affected: www.sanity.io
Timeline · 2 updates
-
investigating Mar 06, 2026, 06:39 PM UTC
Our sales contact form on www.sanity.io is currently inoperative. We are working to restore functionality.
-
resolved Mar 06, 2026, 06:55 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 11:10 PM UTC
- Resolved
- Mar 02, 2026, 11:10 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 03, 2026, 12:23 AM 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.
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 11:07 AM UTC
- Resolved
- Feb 24, 2026, 12:06 PM UTC
- Duration
- 58m
Affected: Media LibraryAsset PipelineStudio
Timeline · 4 updates
-
investigating Feb 24, 2026, 11:29 AM UTC
We are aware of elevated errors with the uploading of assets for some customers, and are currently investigating.
-
monitoring Feb 24, 2026, 11:32 AM UTC
We can see that error levels have returned to normal, and are continuing to monitor.
-
monitoring Feb 24, 2026, 11:45 AM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 24, 2026, 12:06 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 09:56 AM UTC
- Resolved
- Feb 24, 2026, 03:58 PM UTC
- Duration
- 6h 2m
Affected: api.sanity.ioStudio
Timeline · 5 updates
-
investigating Feb 24, 2026, 09:56 AM 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.
-
monitoring Feb 24, 2026, 10:29 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Feb 24, 2026, 11:11 AM UTC
We are continuing to monitor for any further issues.
-
monitoring Feb 24, 2026, 01:14 PM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 24, 2026, 03:58 PM UTC
The incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 07:53 PM UTC
- Resolved
- Feb 19, 2026, 08:46 PM UTC
- Duration
- 52m
Affected: api.sanity.ioapicdn.sanity.io
Timeline · 3 updates
-
investigating Feb 19, 2026, 07:53 PM 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.
-
monitoring Feb 19, 2026, 08:19 PM 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.
-
resolved Feb 19, 2026, 08:46 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 06:45 PM UTC
- Resolved
- Feb 18, 2026, 07:43 PM UTC
- Duration
- 58m
Affected: Studio
Timeline · 3 updates
-
identified Feb 18, 2026, 06:45 PM 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.
-
monitoring Feb 18, 2026, 07:22 PM UTC
The dependency maintainer has implemented a fix, and we are currently monitoring the results.
-
resolved Feb 18, 2026, 07:43 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 01:50 PM UTC
- Resolved
- Feb 10, 2026, 01:39 PM UTC
- Duration
- 23h 48m
Affected: Dataset Management
Timeline · 6 updates
-
identified Feb 09, 2026, 01:50 PM 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 History view in the Sanity Studio. People may see the wrong document revision when querying by transaction ID or an inaccurate chronological order when viewing history entries. We will keep you posted as a fix is being implemented.
-
identified Feb 09, 2026, 02:34 PM UTC
We are continuing to work on a fix for this issue.
-
identified Feb 09, 2026, 03:12 PM UTC
We are continuing to work on a fix for this issue.
-
identified Feb 09, 2026, 03:54 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Feb 09, 2026, 04:21 PM 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.
-
resolved Feb 10, 2026, 01:39 PM UTC
The issue has been resolved. All affected customer datasets have been remediated and the service is operating normally.
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 10:23 AM UTC
- Resolved
- Feb 04, 2026, 11:17 AM UTC
- Duration
- 53m
Affected: Content AgentCanvas
Timeline · 3 updates
-
investigating Feb 04, 2026, 10:23 AM 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.
-
monitoring Feb 04, 2026, 10:42 AM UTC
A fix in our upstream AI provider has been implemented and we are monitoring the results.
-
resolved Feb 04, 2026, 11:17 AM UTC
This incident is resolved. Our upstream AI provider has recovered and Content Agent and Canvas error rates have returned to normal.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 03:54 PM UTC
- Resolved
- Feb 03, 2026, 04:08 PM UTC
- Duration
- 14m
Affected: Content AgentCanvas
Timeline · 3 updates
-
investigating Feb 03, 2026, 03:54 PM 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.
-
identified Feb 03, 2026, 03:57 PM UTC
The issue in our upstream AI provider has been identified and a fix is being implemented.
-
resolved Feb 03, 2026, 04:08 PM 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.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 04:50 PM UTC
- Resolved
- Jan 20, 2026, 09:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 22, 2026, 04:50 PM 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 latest version should be 5.2.1.
Read the full incident report →
- Detected by Pingoru
- Jan 20, 2026, 05:32 PM UTC
- Resolved
- Jan 20, 2026, 05:58 PM UTC
- Duration
- 25m
Affected: Content AgentCanvas
Timeline · 2 updates
-
investigating Jan 20, 2026, 05:32 PM 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.
-
resolved Jan 20, 2026, 05:58 PM UTC
This incident is resolved. Our upstream AI provider has recovered, and Content Agent and Canvas error rates have returned to normal.
Read the full incident report →
- Detected by Pingoru
- Jan 14, 2026, 10:48 AM UTC
- Resolved
- Jan 14, 2026, 11:34 AM UTC
- Duration
- 46m
Affected: Dashboard
Timeline · 2 updates
-
investigating Jan 14, 2026, 10:48 AM 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.
-
resolved Jan 14, 2026, 11:34 AM UTC
This issue has now been resolved. A fix has been implemented and deployed with Sanity Studio version 5.3.1.
Read the full incident report →
- Detected by Pingoru
- Jan 05, 2026, 02:05 PM UTC
- Resolved
- Jan 05, 2026, 02:43 PM UTC
- Duration
- 37m
Affected: apicdn.sanity.io
Timeline · 3 updates
-
investigating Jan 05, 2026, 02:05 PM 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.
-
monitoring Jan 05, 2026, 02:26 PM 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.
-
resolved Jan 05, 2026, 02:43 PM 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.
Read the full incident report →
- Detected by Pingoru
- Dec 09, 2025, 08:50 AM UTC
- Resolved
- Dec 09, 2025, 09:37 AM UTC
- Duration
- 47m
Affected: api.sanity.ioapicdn.sanity.io
Timeline · 3 updates
-
investigating Dec 09, 2025, 09:03 AM 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.
-
monitoring Dec 09, 2025, 09:16 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 09, 2025, 09:37 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 08, 2025, 09:50 AM UTC
- Resolved
- Dec 08, 2025, 06:58 PM UTC
- Duration
- 9h 8m
Affected: Partner Integrations
Timeline · 4 updates
-
identified Dec 08, 2025, 09:50 AM 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
-
monitoring Dec 08, 2025, 10:16 AM UTC
Our team has applied the required updates, and are awaiting further guidance from Vercel.
-
monitoring Dec 08, 2025, 06:57 PM UTC
Updates have been applied and confirmed by Vercel. This incident has been resolved.
-
resolved Dec 08, 2025, 06:58 PM UTC
This incident has been resolved.
Read the full incident report →
