Sanity incident: Content Agent - Delivery issue with some longer-running threads

Affected components

• Content Agent

1. resolvedMay 29, 2026, 15:14 UTC

   This incident has now been resolved.

2. monitoringMay 29, 2026, 10:03 UTC

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

3. identifiedMay 29, 2026, 09:21 UTC

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

4. investigatingMay 29, 2026, 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Sanity's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• ReadMe: Refactored Hubs DownMajor · May 28, 2026, 14:35 UTC
• Elasticsearch: Upstream Azure Outage Causing Service DegradationMajor · May 29, 2026, 06:32 UTC
• Snowflake: Azure - West US 2 (Washington): INC0157956Major · May 29, 2026, 06:47 UTC
• Confluent Cloud: Elevated error rates and latencies in Azure westus2 regionMajor · May 29, 2026, 06:47 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
• ClickHouse Cloud: New service provisioning may fail in AzureMinor · May 28, 2026, 18:26 UTC

How often does Sanity have incidents?

Sanity reported 10 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 52 min. See Sanity's uptime and incident history