Sanity local development blocked - DNS workaround needed
Thanks for sharing that workaround! You're describing a DNS resolution issue that was impacting Sanity users, particularly those using Cloudflare DNS. This was indeed a real incident that occurred on March 29, 2024.
Based on the thread you referenced, the issue was caused by Cloudflare incorrectly flagging cdn.sanity.io (and related domains like cdn-tmp.i-p-s4y.com) as malware. This affected users who had Cloudflare DNS configured, preventing them from accessing Sanity content in both production and development environments.
The temporary workaround you mentioned was spot on - switching to an alternative DNS provider like Google's 8.8.8.8 allowed developers to continue working while the issue was being investigated.
What happened: The Sanity operations team worked directly with Cloudflare to resolve the false positive malware flagging. The issue was resolved within a few hours, though some users needed to wait for DNS cache TTL to expire before seeing the fix take effect.
For future reference: If you encounter similar DNS-related issues with Sanity services:
- Check if it's DNS-specific by trying alternative DNS servers (8.8.8.8, 1.1.1.1, etc.)
- Report it in the Sanity community Slack where the team monitors actively
- Check Sanity's status page for any ongoing incidents
The incident highlighted how third-party DNS filtering can sometimes cause unexpected outages, even when Sanity's infrastructure is functioning normally. Good catch on identifying the DNS workaround - that's exactly the kind of troubleshooting that helps unblock teams quickly!
Show original thread26 replies
Sanity – Build the way you think, not the way your CMS thinks
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.