Historial de interrupciones de Sanity

1. September 1, 2026 at 7:31 AM UTCidentified

   Hemos identificado un problema evitando que el formulario de pago se cargue en Gestion. Los clientes sin tarjeta guardada no pueden añadir un método de pago o actualizar su plan. Las suscripciones existentes y los métodos de pago guardados no están afectados. Se ha identificado la causa y se está implementando una solución. Publicaremos una actualización una vez que esté en vivo.

2. September 1, 2026 at 7:35 AM UTCmonitoring

   La solución ha sido implementada y el formulario de pago es restaurado. Estamos verificando los flujos afectados y el monitoreo para cualquier otro problema.

3. September 1, 2026 at 7:46 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 27, 2026 at 7:59 AM UTCresolved

   A partir de aprox. 6:33 UTC , vimos tasas de error elevadas (HTTP 5xxx) en solicitudes al servicio del Índice de Embeddings. La cuestión fue identificada y resuelta aproximadamente a las 7:16 UTC.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 26, 2026 at 9:14 PM UTCresolved

   A partir de aprox. 19:51 UTC, vimos tasas de error elevadas (HTTP 5xxx) en solicitudes al Índice de Embeddings, Acciones Agente y Servicios AI Assist. La cuestión se identificó y resolvió aproximadamente a las 20:32 UTC.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 20, 2026 at 2:33 PM UTCresolved

   A partir de aproximadamente 13:05–13:45 UTC, vimos altas tasas de error de API para un pequeño subconjunto de clientes debido a los timeouts intermitentes en las solicitudes de API. La cuestión ha sido identificada y resuelta.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 17, 2026 at 8:54 AM UTCresolved

   Algunos clientes experimentaron problemas intermitentes de conectividad Studio entre aproximadamente 07:25 y 07:45 UTC el 17 de agosto. La cuestión se ha resuelto y los servicios han regresado a una operación normal.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 14, 2026 at 2:46 PM UTCinvestigating

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

2. August 14, 2026 at 2:53 PM UTCmonitoring

   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. August 14, 2026 at 3:32 PM UTCresolved

   This incident has been resolved.

1. August 6, 2026 at 12:46 PM UTCresolved

   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.

1. July 25, 2026 at 12:37 AM UTCresolved

   Entre aproximadamente 23:16 UTC los días 24 y 00:10 UTC el 25 de julio, algunas solicitudes de imágenes y activos servidos de cdn.sanity. io devolvió errores o cargado lentamente para los usuarios en América del Norte y Europa. Image and asset delivery has since returned to normal operation. Las API de contenido (api.sanity.io, apicdn.sanity.io) y la edición de estudio no se vieron afectadas.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 9:56 PM UTCresolved

   Entre las 18:00 y las 21:00 UTC, experimentamos interrupciones parciales en la API de contenido en vivo en algunas regiones. El incidente ya está resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 11:45 AM UTCinvestigating

   Estamos investigando informes de problemas de conectividad que afectan a Sanity Studio. Algunos usuarios pueden experimentar que el Studio se atasca en "Tratar de conectar" o no cargar. Nuestro equipo de ingeniería está investigando activamente el tema y proporcionaremos actualizaciones tan pronto como esté disponible más información.

2. July 22, 2026 at 1:22 PM UTCinvestigating

   Hemos identificado que la cuestión ha recurrido para algunos usuarios después de la mitigación anterior. Nuestro equipo de ingeniería está investigando activamente los problemas de conectividad restantes y trabajando para restaurar el servicio completo. Seguiremos proporcionando actualizaciones a medida que se disponga de más información.

3. July 22, 2026 at 3:11 PM UTCidentified

   Hemos identificado una repetición del problema que afecta a servicios adicionales. Nuestro equipo de ingeniería está implementando activamente nuevas medidas de mitigación e investigando el impacto restante. Seguiremos proporcionando actualizaciones a medida que estén disponibles.

4. July 22, 2026 at 3:52 PM UTCidentified

   Seguimos trabajando para solucionar este problema.

5. July 22, 2026 at 3:53 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

6. July 22, 2026 at 6:05 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 21, 2026 at 4:32 PM UTCinvestigating

   Actualmente estamos investigando un problema donde la página Webhooks no puede cargar datos de webhook. Esto no afecta la entrega de webhook. Webhooks configurados en su proyecto continuará disparando como se espera.

2. July 21, 2026 at 6:11 PM UTCmonitoring

   Se ha aplicado una solución, y estamos monitoreando los resultados.

3. July 21, 2026 at 7:22 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 26, 2026 at 9:53 AM UTCresolved

   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.

1. June 15, 2026 at 8:49 AM UTCinvestigating

   We are currently investigating an issue causing slower-than-expected query performance for some customers. A subset of users may experience increased latency when querying content. Our team is actively investigating the issue and working to mitigate the impact. We will provide further updates as more information becomes available.

2. June 15, 2026 at 8:50 AM UTCidentified

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

3. June 15, 2026 at 8:51 AM UTCmonitoring

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

4. June 15, 2026 at 10:39 AM UTCresolved

   This incident has been resolved.

1. May 29, 2026 at 9:19 AM UTCinvestigating

   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. May 29, 2026 at 9:21 AM UTCidentified

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

3. May 29, 2026 at 10:03 AM UTCmonitoring

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

4. May 29, 2026 at 3:14 PM UTCresolved

   This incident has now been resolved.

1. May 1, 2026 at 12:34 PM UTCinvestigating

   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. May 1, 2026 at 12:46 PM UTCidentified

   We are implementing a fix that should resolve the issue.

3. May 1, 2026 at 12:48 PM UTCidentified

   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. May 1, 2026 at 1:08 PM UTCidentified

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

5. May 1, 2026 at 1:11 PM UTCmonitoring

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

6. May 1, 2026 at 1:19 PM UTCresolved

   This incident has been resolved.

1. April 14, 2026 at 7:49 AM UTCresolved

   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.

1. April 13, 2026 at 7:45 AM UTCresolved

   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.

1. April 6, 2026 at 3:27 PM UTCresolved

   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.

1. April 3, 2026 at 1:38 PM UTCinvestigating

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

2. April 3, 2026 at 2:37 PM UTCmonitoring

   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. April 3, 2026 at 7:45 PM UTCresolved

   This incident has been resolved.

1. March 22, 2026 at 1:58 PM UTCinvestigating

   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. March 22, 2026 at 2:23 PM UTCidentified

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

3. March 22, 2026 at 2:48 PM UTCmonitoring

   A fix has been implemented and we are monitoring results.

4. March 22, 2026 at 4:42 PM UTCresolved

   This incident has been resolved.