BREAKING: Supabase MINOR π‘ Storage latency in US-West-2 [zwmwcs0r4hll]
Supabase Storage users in US-West-2 experiencing increased latency. Immediate workarounds for indie hackers inside.
BREAKING: Supabase Storage Latency in US-West-2
Status: IDENTIFIED | Severity: MINOR | Region: US-West-2 Only
---
What's Down & Who's Affected
Supabase is currently experiencing increased latency on storage requests for users operating in the US-West-2 region. This affects file uploads, downloads, and metadata operations through the Storage API.
Affected:
us-west-2NOT Affected:
---
Immediate Workarounds (Do This Now)
1. Implement Client-Side Retry Logic
```javascript const uploadWithRetry = async (file, maxRetries = 3) => { for (let i = 0; i < maxRetries; i++) { try { return await supabase.storage .from('bucket') .upload(path/${file.name}, file, {
timeout: 60000 // Increase timeout to 60s
});
} catch (error) {
if (i < maxRetries - 1) {
await new Promise(r => setTimeout(r, 1000 * (i + 1)));
} else throw error;
}
}
};
```2. Increase Request Timeouts
Update your storage client configuration to wait longer: ```javascript const { data, error } = await supabase.storage .from('bucket') .download('file.pdf', { timeout: 120000 }); // 2 minutes ```3. Queue Non-Critical Uploads
Defer non-urgent file operations to off-peak hours using a job queue (Bull, Inngest, or similar).4. Redirect to CDN Cache
If serving existing files, route requests through your CDN cache first before hitting Supabase Storage.5. Rate Limit Client Requests
Avoid overwhelming the region further: ```javascript const pLimit = require('p-limit'); const limit = pLimit(2); // Max 2 concurrent uploads const uploads = files.map(f => limit(() => uploadWithRetry(f))); ```---
How to Check If You're Affected
1. Check your project region in Supabase Dashboard β Settings β General 2. Run a test upload: ```bash curl -X POST https://[project].supabase.co/storage/v1/object/test-file \ -H "Authorization: Bearer [token]" \ -d "test" \ -w "\nResponse time: %{time_total}s\n" ``` 3. Monitor response times β expect 5-15 second delays instead of <500ms 4. Check Supabase status page: status.supabase.com
---
Alternative Tools to Consider (Short-term)
Note: Don't migrate yet. This is identified and likely temporary.
---
How to Monitor Recovery
1. Official updates: [status.supabase.com](https://status.supabase.com) 2. Discord community: supabase.com/discord (check #incidents) 3. Monitor your own metrics: - Track upload times in your app - Set up alerts for >5s response times - Test recovery with the curl command above
Expected resolution: Within 2-4 hours based on similar incidents.
---
Bottom Line
This is a regional latency issue, not a data loss risk. Implement retry logic, increase timeouts, and queue non-urgent operations. Your data is safe. Monitor the status page and expect recovery soon.
Stay calm. Keep shipping.