Slow Sanity response times (4-5s vs <100ms) - any known issues?

I totally understand how frustrating that must be! Going from <100ms to 4-5 seconds is a huge jump. Here are some things to check:

First, check the status page:

Sanity maintains a status page at status.sanity.io where they report any ongoing incidents or degraded performance. This should be your first stop to see if there's a platform-wide issue affecting response times on apicdn.sanity.io or other services.

Common causes for sudden slowdowns:

1. CDN vs non-CDN requests - Make sure you're using useCdn: true in your Sanity client configuration for read operations. The CDN endpoint (apicdn.sanity.io) is much faster than the direct API endpoint for queries, with intelligent caching at the edge. If something changed in your config, this could explain the slowdown.

2. Query changes - Did you recently deploy any changes to your GROQ queries? Even small modifications can impact performance, especially with larger datasets. Check for:

   • New deep reference resolution (multiple levels of ->)
   • Added sorting operations on non-indexed fields
   • Increased result set sizes without pagination

3. Dataset growth - If your content has grown significantly, queries that were fast before might now be hitting performance limits. The query optimization documentation covers techniques like efficient filtering, limiting projections to only the fields you need, and reducing deep nested queries.

4. Authentication tokens - If you recently switched from using CDN-cached queries to authenticated queries (with tokens), you'll bypass the CDN cache and hit the API directly, which is slower but provides fresher data.

What to do next:

• Check status.sanity.io for any reported incidents from yesterday
• Review your Sanity client configuration (especially useCdn setting)
• Check your query logs to see which specific queries are slow
• Look at your recent deployments to see if any code changes coincide with when the slowdown started
• If it's not a known issue and you can't identify the cause, contact Sanity support with specific examples of slow queries, your project ID, and timestamps of when the slowdown began - they can investigate API-level issues

The fact that this started "yesterday" suggests it might be either a platform issue (check the status page first) or a recent deployment on your end. If you haven't changed anything, definitely reach out to support with your project details so they can investigate!