Sanity Outage History
Sanity is up right nowPingoru has recorded 59 incidents for Sanity: 56 in the last 12 months and 14 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 4 | 7 of 720 (1%) |
| May 2026 | 3 | 7 of 744 (1%) |
| June 2026 | 2 | 4 of 720 (1%) |
| July 2026 | 4 | 13 of 744 (2%) |
| August 2026 | 6 | 17 of 744 (2%) |
| September 2026 | 4 | 3 of 720 (0%) |
| October 2026 | 4 | 43 of 592 (7%) |
Incidents, newest first
Minor April 6, 2026 Elevated API Error Rates 20m
Started Apr 06, 2026, 02:00 PM UTC· resolved Apr 06, 2026, 02:20 PM UTC
- 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.
Minor April 3, 2026 Issues with Loading Document Lists in Sanity Studio 6h 6m Studio
Started Apr 03, 2026, 01:38 PM UTC· resolved Apr 03, 2026, 07:45 PM UTC
- 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.
Major March 22, 2026 Elevated error rates on the Asset CDN 2h 43m cdn.sanity.io
Started Mar 22, 2026, 01:58 PM UTC· resolved Mar 22, 2026, 04:42 PM UTC
- 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.
Major March 12, 2026 Issue with login via SSO/SAML 1h 38m Authentication
Started Mar 12, 2026, 12:11 PM UTC· resolved Mar 12, 2026, 01:49 PM UTC
- 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.
Notice March 6, 2026 Contact forms unavailable 16m www.sanity.io
Started Mar 06, 2026, 06:39 PM UTC· resolved Mar 06, 2026, 06:55 PM UTC
- 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.
Notice March 2, 2026 APICDN Elevated Latency 7h 10m
Started Mar 02, 2026, 04:00 PM UTC· resolved Mar 02, 2026, 11:10 PM UTC
- 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.
Minor February 24, 2026 Elevated error rates with asset upload 58m Media Library, Asset Pipeline, Studio
Started Feb 24, 2026, 11:07 AM UTC· resolved Feb 24, 2026, 12:06 PM UTC
- 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.
Minor February 19, 2026 Elevated API and API CDN errors and latency for some customers 52m api.sanity.io, apicdn.sanity.io
Started Feb 19, 2026, 07:53 PM UTC· resolved Feb 19, 2026, 08:46 PM UTC
- 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.
Major February 18, 2026 Installation issues affecting the Sanity package 58m Studio
Started Feb 18, 2026, 06:45 PM UTC· resolved Feb 18, 2026, 07:43 PM UTC
- 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.
Minor February 9, 2026 History API inconsistencies 23h 48m Dataset Management
Started Feb 09, 2026, 01:50 PM UTC· resolved Feb 10, 2026, 01:39 PM UTC
- 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.
Major February 4, 2026 Content Agent and Canvas elevated error rate 53m Content Agent, Canvas
Started Feb 04, 2026, 10:23 AM UTC· resolved Feb 04, 2026, 11:17 AM UTC
- 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.
Major February 3, 2026 Content Agent and Canvas experiencing elevated error rates 14m Content Agent, Canvas
Started Feb 03, 2026, 03:54 PM UTC· resolved Feb 03, 2026, 04:08 PM UTC
- 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.
Minor January 20, 2026 Content Agent & Canvas experiencing elevated error rates 25m Content Agent, Canvas
Started Jan 20, 2026, 05:32 PM UTC· resolved Jan 20, 2026, 05:58 PM UTC
- 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.
Notice January 20, 2026 Sanity CLI init flow regression –
Started Jan 20, 2026, 09:00 AM UTC· resolved Jan 20, 2026, 09:00 AM UTC
- 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.
Minor January 14, 2026 Content Releases & Scheduled Drafts - Sameorigin error when accessing via Dashboard 46m Dashboard
Started Jan 14, 2026, 10:48 AM UTC· resolved Jan 14, 2026, 11:34 AM UTC
- 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.
Minor January 5, 2026 Elevated error rates on our API CDN 37m apicdn.sanity.io
Started Jan 05, 2026, 02:05 PM UTC· resolved Jan 05, 2026, 02:43 PM UTC
- 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.
Minor December 9, 2025 Elevated API and API CDN error rate for a small subset of customers 47m api.sanity.io, apicdn.sanity.io
Started Dec 09, 2025, 08:50 AM UTC· resolved Dec 09, 2025, 09:37 AM UTC
- 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.
Major December 8, 2025 Vercel - Unable to create new Sanity integrations 9h 8m Partner Integrations
Started Dec 08, 2025, 09:50 AM UTC· resolved Dec 08, 2025, 06:58 PM UTC
- 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.
Notice December 3, 2025 Security vulnerability identified with React Server Components 1d 2h
Started Dec 03, 2025, 07:37 PM UTC· resolved Dec 04, 2025, 10:12 PM UTC
- investigating Dec 03, 2025, 07:37 PM UTC
A security vulnerability (CVE-2025-55182) affecting React Server Components (RSC) and several related packages including Next.js was disclosed today by the React Team (https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components). Our Impact: Vercel has already rolled out platform-level protections and preventative measures. We are acting proactively and have started rolling out fixes across our platform and services as well. Required Action: Sanity studio deployments are not affected and require no action. If your Studio is deployed using Next.js, please follow the recommended steps outlined here: https://vercel.com/changelog/cve-2025-55182#resolution.
- monitoring Dec 03, 2025, 08:48 PM UTC
Our team has applied the initial recommended updates from the React Team regarding the recent vulnerability. We are actively completing remaining internal package updates and closely monitoring any further guidance from React and Vercel. Required Action for Next Studio Deployments: Note: Sanity Studio deployments are not affected and require no action. If your Studio is deployed using Next.js, please follow the recommended steps outlined here: https://vercel.com/changelog/cve-2025-55182#resolution
- resolved Dec 04, 2025, 10:12 PM UTC
We have completed dependency updates per guidance from Vercel and the React team. Sanity studio deployments are not affected and require no action. If your Studio is deployed using Next.js, please follow the recommended steps outlined here: https://vercel.com/changelog/cve-2025-55182#resolution.
Notice November 6, 2025 Issues with updating studio to 4.14.0 for studios using React 18 53m
Started Nov 06, 2025, 05:29 PM UTC· resolved Nov 06, 2025, 06:23 PM UTC
- identified Nov 06, 2025, 05:29 PM UTC
The issue has been identified due to a dependency issue with studios utilizing React 18. Our team is working towards a fix and have rolled back the affected version.
- resolved Nov 06, 2025, 06:23 PM UTC
Peer dependencies added to handle React 18.
Minor October 29, 2025 Increased errors and failure to load images 39m cdn.sanity.io, Asset Pipeline
Started Oct 29, 2025, 09:53 PM UTC· resolved Oct 29, 2025, 10:33 PM UTC
- monitoring Oct 29, 2025, 09:53 PM UTC
Starting at approximately 21:05 UTC, we experienced an increase in errors while serving images from cdn.sanity.io. We have successfully mitigated the issue, and services began returning to normal around 21:35 UTC. Our team will continue to closely monitor the CDN.
- resolved Oct 29, 2025, 10:33 PM UTC
This issue is now resolved and the CDN is operating normally. Apologies for the turbulence!
Major October 20, 2025 AWS partial outage impacting Sanity logins, Dashboard, and Manage interface 1h 51m Authentication, Dashboard, Manage
Started Oct 20, 2025, 09:20 AM UTC· resolved Oct 20, 2025, 11:11 AM UTC
- monitoring Oct 20, 2025, 10:10 AM UTC
Following an operational issue in AWS, from 07:30 UTC to 09:18 UTC people experienced intermittent issues logging in and out of Sanity, accessing the Sanity Dashboard, and using the Manage interface. All other services, including functions, mutations, and queries to the API and API CDN were unaffected by this incident. Service stability is now restored but we are continuing to monitor closely.
- resolved Oct 20, 2025, 11:11 AM UTC
This incident has been resolved.
Major October 16, 2025 HTTP 404 Responses with AI Assist 2h 8m AI Assist
Started Oct 16, 2025, 01:21 PM UTC· resolved Oct 16, 2025, 03:29 PM UTC
- investigating Oct 16, 2025, 01:21 PM UTC
We are aware of customers experiencing HTTP 404 responses when using AI Assist within Sanity Studio, and are currently investigating.
- identified Oct 16, 2025, 01:55 PM UTC
We have identified an issue with a downstream service, and are working to resolve this.
- identified Oct 16, 2025, 02:35 PM UTC
We are continuing to work on a fix for this issue.
- identified Oct 16, 2025, 03:06 PM UTC
We are continuing to work on a fix for this issue.
- resolved Oct 16, 2025, 03:29 PM UTC
A fix has been implemented, and we can confirm that AI Assist functionality has returned to normal.
Major October 14, 2025 Elevated HTTP 429 rate-limit errors on API and API CDN 39m api.sanity.io, apicdn.sanity.io
Started Oct 14, 2025, 11:02 AM UTC· resolved Oct 14, 2025, 11:41 AM UTC
- investigating Oct 14, 2025, 11:02 AM UTC
We are aware of customers experiencing HTTP 429 rate limiting on our API, and are currently investigating.
- identified Oct 14, 2025, 11:08 AM UTC
We are addressing renewed 429 error spikes that are impacting customers globally. These errors are surfacing as rate-limit errors for queries to both the API and API CDN.
- monitoring Oct 14, 2025, 11:15 AM UTC
A fix has been implemented, and we are observing that requests have now returned to normal. We are continuing to monitor.
- resolved Oct 14, 2025, 11:41 AM UTC
This incident has been resolved; API error rates returned to normal at 11:07 UTC after the fix was implemented.