BREAKING: Supabase US-West-2 Storage Experiencing Increased Latency

Supabase Storage users in US-West-2 region reporting elevated latency on storage requests. Immediate workarounds and mitigation steps inside.

Incident Summary

Supabase is currently experiencing increased latency on Storage requests for users in the US-West-2 region. This is an active monitoring alert affecting file upload, download, and retrieval operations.

What's Affected

Other regions and services (PostgreSQL, Auth, Realtime) appear unaffected at this time.

How to Check If You're Affected

1. Check your region: Navigate to your Supabase project settings → General → Region. If it shows "us-west-2", you may experience degraded performance. 2. Monitor response times: Check your application logs for storage operation durations exceeding typical baselines. 3. Check Supabase Status Page: Visit [status.supabase.com](https://status.supabase.com) for real-time updates.

Immediate Workarounds

For Active Applications

1. Implement retry logic with exponential backoff ```javascript // Add retry logic to storage operations const retryStorageCall = async (fn, maxRetries = 3) => { for (let i = 0; i < maxRetries; i++) { try { return await fn(); } catch (error) { if (i === maxRetries - 1) throw error; await new Promise(r => setTimeout(r, Math.pow(2, i) * 1000)); } } }; ```

2. Increase timeout thresholds in your client configurations (if applicable).

3. Batch storage operations to reduce request volume during peak latency.

4. Implement caching for frequently accessed files to reduce origin requests.

Temporary Alternatives (if latency is critical)

1. Use a different region: If acceptable, migrate your project to another region (us-east-1, eu-west-1, etc.) temporarily. Note: This requires data migration planning.

2. Third-party storage providers: Temporarily redirect storage operations to: - AWS S3 - Google Cloud Storage - Cloudflare R2 - Azure Blob Storage

3. Queue non-critical uploads: Defer non-essential storage operations until latency normalizes.

Monitoring & Updates

Unknown Details

I cannot confirm:

These specifics should be available on the official Supabase status page and their incident documentation.

Next Steps

1. Contact Supabase Support if latency impacts your production services (Pro+ plans receive priority support) 2. Document baseline metrics to measure improvement once resolved 3. Review your region choice for future deployments based on your user base

Last Updated: Check status.supabase.com for the most current information.