Sharp uptick in "invalid response from upstream server" errors

I understand you're experiencing "invalid response from upstream server" errors across multiple services. This type of error typically indicates an issue with Sanity's infrastructure or connectivity between services.

Here are the steps I'd recommend to troubleshoot and get help:

Immediate Actions:

1. Check Sanity's Status Page - Visit https://status.sanity.io to see if there are any ongoing incidents or degraded performance reports. Upstream server errors often correlate with platform-wide issues.

2. Check Which Services Are Affected - Since you mentioned two separate services are reporting this, identify:

   • Are these errors coming from API requests (apicdn.sanity.io or api.sanity.io)?
   • Are they related to Studio, asset delivery, or Content Lake queries?
   • What specific endpoints or operations are failing?

3. Review Your Network Path - "Upstream server" errors can sometimes indicate:

   • CDN or proxy issues between your application and Sanity's infrastructure
   • DNS resolution problems
   • Temporary network connectivity issues

Gathering Diagnostic Information:

For your thread, include these details to help diagnose:

• Exact error messages and HTTP status codes (502, 503, 504?)
• Timestamps when errors started
• Your project ID (if comfortable sharing)
• Whether errors are intermittent or consistent
• Any recent changes to your configuration or deployment

Getting Help:

Since this appears to be an infrastructure issue affecting multiple services:

• Post in the Sanity Community Slack #help channel with your details
• If you're on a paid plan, contact support@sanity.io directly
• Check the Activity Feed in your project to see if there are any unusual platform activities

The API CDN is globally distributed and designed for high reliability, so widespread "upstream server" errors are unusual and likely indicate either a temporary platform issue or a specific configuration problem that support can help resolve quickly.

Keep us posted in your thread with what you find - this helps others who might encounter similar issues!