Sanity Outage History

Sanity is up right now

Sanity had 43 outages in the last 2 years totaling 69h 0m of downtime — averaging 1.8 incidents per month.

There were 43 Sanity outages since June 11, 2025 totaling 69h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.sanity.io

Notice December 3, 2025

Security vulnerability identified with React Server Components

Detected by Pingoru
Dec 03, 2025, 07:37 PM UTC
Resolved
Dec 04, 2025, 10:12 PM UTC
Duration
1d 2h
Timeline · 3 updates
  1. 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.

  2. 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

  3. 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.

Read the full incident report →

Minor November 17, 2025

Elevated API error rates for some customers

Detected by Pingoru
Nov 17, 2025, 08:52 AM UTC
Resolved
Nov 17, 2025, 09:41 AM UTC
Duration
48m
Affected: api.sanity.ioapicdn.sanity.io
Timeline · 3 updates
  1. investigating Nov 17, 2025, 09:06 AM UTC

    Starting 08:45 UTC, a small subset of customers are intermittently experiencing 504 errors (gateway time-outs) using the query and mutate endpoints. We are currently investigating this issue.

  2. monitoring Nov 17, 2025, 09:24 AM UTC

    Error levels have returned to normal at 09:00 UTC and people should no longer experience issues. We will continue monitoring closely for some time before marking the incident as resolved.

  3. resolved Nov 17, 2025, 09:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 6, 2025

Issues with updating studio to 4.14.0 for studios using React 18

Detected by Pingoru
Nov 06, 2025, 05:29 PM UTC
Resolved
Nov 06, 2025, 06:23 PM UTC
Duration
53m
Timeline · 2 updates
  1. 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.

  2. resolved Nov 06, 2025, 06:23 PM UTC

    Peer dependencies added to handle React 18.

Read the full incident report →

Minor November 6, 2025

Elevated API and API CDN error rate for some customers

Detected by Pingoru
Nov 06, 2025, 08:40 AM UTC
Resolved
Nov 06, 2025, 10:34 AM UTC
Duration
1h 54m
Affected: api.sanity.ioapicdn.sanity.io
Timeline · 5 updates
  1. investigating Nov 06, 2025, 08:40 AM UTC

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

  2. investigating Nov 06, 2025, 09:07 AM UTC

    While error rates have improved we are still seeing elevated numbers and are continuing to investigate this issue.

  3. investigating Nov 06, 2025, 09:27 AM UTC

    We are continuing to investigate the issue.

  4. monitoring Nov 06, 2025, 09:47 AM UTC

    A fix has been implemented and error rates have returned to normal as of 09:40 UTC. We continue monitoring results.

  5. resolved Nov 06, 2025, 10:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 29, 2025

Increased errors and failure to load images

Detected by Pingoru
Oct 29, 2025, 09:53 PM UTC
Resolved
Oct 29, 2025, 10:33 PM UTC
Duration
39m
Affected: cdn.sanity.ioAsset Pipeline
Timeline · 2 updates
  1. 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.

  2. resolved Oct 29, 2025, 10:33 PM UTC

    This issue is now resolved and the CDN is operating normally. Apologies for the turbulence!

Read the full incident report →

Major October 20, 2025

AWS partial outage impacting Sanity logins, Dashboard, and Manage interface

Detected by Pingoru
Oct 20, 2025, 09:20 AM UTC
Resolved
Oct 20, 2025, 11:11 AM UTC
Duration
1h 51m
Affected: AuthenticationDashboardManage
Timeline · 2 updates
  1. 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.

  2. resolved Oct 20, 2025, 11:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 16, 2025

HTTP 404 Responses with AI Assist

Detected by Pingoru
Oct 16, 2025, 01:21 PM UTC
Resolved
Oct 16, 2025, 03:29 PM UTC
Duration
2h 8m
Affected: AI Assist
Timeline · 5 updates
  1. 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.

  2. identified Oct 16, 2025, 01:55 PM UTC

    We have identified an issue with a downstream service, and are working to resolve this.

  3. identified Oct 16, 2025, 02:35 PM UTC

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

  4. identified Oct 16, 2025, 03:06 PM UTC

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

  5. 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.

Read the full incident report →

Major October 14, 2025

Elevated HTTP 429 rate-limit errors on API and API CDN

Detected by Pingoru
Oct 14, 2025, 11:02 AM UTC
Resolved
Oct 14, 2025, 11:41 AM UTC
Duration
39m
Affected: api.sanity.ioapicdn.sanity.io
Timeline · 4 updates
  1. 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.

  2. 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.

  3. 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.

  4. 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.

Read the full incident report →

Critical October 1, 2025

Sync issues using Sanity Connect for Shopify

Detected by Pingoru
Oct 01, 2025, 03:54 PM UTC
Resolved
Oct 01, 2025, 04:39 PM UTC
Duration
45m
Affected: Partner Integrations
Timeline · 2 updates
  1. investigating Oct 01, 2025, 03:54 PM UTC

    We are currently experiencing an issue where data is not syncing between Shopify and Sanity when using Sanity Connect for Shopify. We are investigating and working on a fix.

  2. resolved Oct 01, 2025, 04:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 10, 2025

Issue with annotations in Portable Text Editor on Studio v4.8.0

Detected by Pingoru
Sep 10, 2025, 06:40 PM UTC
Resolved
Sep 10, 2025, 05:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 10, 2025, 06:40 PM UTC

    We experienced a regression on v4.8.0 of the Studio affecting annotations in the Portable Text Editor. Specifically, people reported an issue where their selection in the annotation was not recorded as expected. We have released a fix in a new version (v4.8.1) and deprecated the faulty v4.8.0 release on NPM. Apologies for any impact this issue had on your content operations.

Read the full incident report →

Major September 10, 2025

Project access issues for some users

Detected by Pingoru
Sep 10, 2025, 11:03 AM UTC
Resolved
Sep 10, 2025, 11:47 AM UTC
Duration
43m
Affected: AuthenticationManage
Timeline · 2 updates
  1. monitoring Sep 10, 2025, 11:03 AM UTC

    Between 10:30 and 10:45 UTC, we experienced an issue with our authentication service impacting a subset of users. This issue affected people's ability to log in to Sanity projects and open the project management interface. It may also have surfaced as false negative CORS origin errors when already logged in to a studio. As of 10:45 UTC, a fix has been implemented and we are monitoring results.

  2. resolved Sep 10, 2025, 11:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 21, 2025

Dataset Copy Failures

Detected by Pingoru
Aug 21, 2025, 05:17 PM UTC
Resolved
Aug 21, 2025, 05:38 PM UTC
Duration
20m
Affected: Dataset Management
Timeline · 2 updates
  1. investigating Aug 21, 2025, 05:17 PM UTC

    We've identified an issue with dataset copying using cloud clone. We're working on mitigating the issue.

  2. resolved Aug 21, 2025, 05:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 4, 2025

Version 3.97.0 of Studio unusable because of a missing package

Detected by Pingoru
Jul 04, 2025, 01:29 PM UTC
Resolved
Jul 04, 2025, 01:46 PM UTC
Duration
16m
Timeline · 2 updates
  1. monitoring Jul 04, 2025, 01:29 PM UTC

    Because of a missing package, updating to Studio version 3.97.0 or installing it will throw an error. The error can affect both local installations and CI environments. We have just released a new version (v3.97.1) and will deprecate the faulty release shortly. While we are taking steps to avoid this issue happening again, to reduce the risk of similar issues we recommend installing NPM dependencies using a lock file, which helps ensure consistency across deployments.

  2. resolved Jul 04, 2025, 01:46 PM UTC

    We have now deprecated all 3.97.0 packages on NPM and people should be able to upgrade to the latest Studio v3.97.1 without issues. Apologies for any impact this issue had on your operations.

Read the full incident report →

Notice July 3, 2025

Dataset Create/Delete Failures

Detected by Pingoru
Jul 03, 2025, 04:20 PM UTC
Resolved
Jul 04, 2025, 04:26 PM UTC
Duration
1d
Timeline · 3 updates
  1. identified Jul 03, 2025, 04:20 PM UTC

    As of June 30th, we've identified an issue with dataset deletions for some customers - datasets aren't properly being disposed of and this limits the ability to create new datasets. We're working on mitigating the issue.

  2. monitoring Jul 04, 2025, 10:13 AM UTC

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

  3. resolved Jul 04, 2025, 04:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 3, 2025

Reports of stale or empty API CDN results

Detected by Pingoru
Jul 03, 2025, 11:10 AM UTC
Resolved
Jul 03, 2025, 11:56 AM UTC
Duration
46m
Affected: apicdn.sanity.io
Timeline · 2 updates
  1. investigating Jul 03, 2025, 11:10 AM UTC

    We are currently investigating reports of stale or empty API CDN results.

  2. resolved Jul 03, 2025, 11:56 AM UTC

    We have confirmed there were no issues with the API CDN during this time and are closing this triage incident.

Read the full incident report →

Minor June 24, 2025

Runtime error for auto-updating Studios on v3.94.0

Detected by Pingoru
Jun 24, 2025, 05:30 PM UTC
Resolved
Jun 24, 2025, 08:15 PM UTC
Duration
2h 44m
Timeline · 3 updates
  1. investigating Jun 24, 2025, 05:30 PM UTC

    Version 3.94.0 of Sanity Studio is failing at runtime when auto-updates are enabled. As a workaround, temporarily disabling auto-updates while manually deploying 3.94.0 should work as expected. We are working on a fix for the issue.

  2. identified Jun 24, 2025, 06:17 PM UTC

    The root cause has been identified and we're implementing a fix. We will have a new release available shortly.

  3. resolved Jun 24, 2025, 08:15 PM UTC

    We have released version 3.94.2 to address the issue with auto-updates and things are back to normal. If you've disabled them, it's recommended to re-enable them in your Studio.

Read the full incident report →

Major June 12, 2025

Google Cloud Platform outage impacting auto-updating Studios, asset services, and Google auth

Detected by Pingoru
Jun 12, 2025, 06:49 PM UTC
Resolved
Jun 12, 2025, 10:35 PM UTC
Duration
3h 45m
Affected: AuthenticationAsset Pipeline
Timeline · 3 updates
  1. identified Jun 12, 2025, 06:49 PM UTC

    A Google Cloud Platform outage is currently impacting auto-updating Studios, the image pipeline, file asset service, and Google authentication. Cached images will continue to be served. API and API CDN endpoints are not currently affected.

  2. monitoring Jun 12, 2025, 07:34 PM UTC

    Google Cloud Platform has mitigated the issues affecting Sanity services, which were impacted from 17:53 UTC to 18:55 UTC. We are continuing to monitor.

  3. resolved Jun 12, 2025, 10:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 11, 2025

Dataset and projectId GROQ functions returned null in webhooks

Detected by Pingoru
Jun 11, 2025, 06:57 PM UTC
Resolved
Jun 11, 2025, 06:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 11, 2025, 06:57 PM UTC

    Between 12:30 and 18:50 UTC, the sanity::dataset and sanity::projectId GROQ functions returned null in GROQ webhook filters and projections. This null value may have caused unexpected GROQ webhook results. The underlying cause has been resolved and additional testing is now in place to prevent this from reoccurring in the future. We apologize for the disruption of operations caused by these unexpected GROQ webhook values.

Read the full incident report →