BREAKING: Supabase Storage Search Failing for Restored Projects

Supabase Storage search functionality is experiencing issues for restored projects. Here are immediate workarounds and status updates.

Issue Summary

Supabase is currently experiencing a monitoring alert for Storage search functionality failing specifically on restored projects. This affects the ability to query and retrieve files from project backups that have been restored to production environments.

What's Affected

Storage Search API: Search operations on restored Supabase projects are failing

Scope: Projects that have undergone restoration/recovery processes

Status: Under active monitoring and investigation

Severity: High for affected users; limited scope to restoration scenarios

How to Check If You're Affected

1. Navigate to your Supabase project dashboard 2. Check if your project was recently restored from backup 3. Attempt a storage search query via the API or dashboard 4. If you receive timeout or "search unavailable" errors, you're likely affected 5. Monitor the [Supabase Status Page](https://status.supabase.com) for official updates

Immediate Workarounds

Workaround 1: Direct File Listing (Instead of Search)

Use the list files endpoint instead of search: ``` GET /storage/v1/b/{bucketName}/o ``` This retrieves all files without search filtering. Filter results client-side if needed.

Workaround 2: Re-index Storage (If Available)

Contact Supabase support to request a storage re-index for your restored project. This may restore search functionality without waiting for the automatic fix.

Workaround 3: Temporary Project Migration

If search is critical:

Export your data from the affected project

Create a new project (don't use restored instance)

Re-import your data fresh

Update connection strings in your application

Workaround 4: Use Alternative Queries

If you know file naming patterns, use prefix-based filtering via list API

Implement application-level search on retrieved file metadata

Use file path patterns instead of full-text search temporarily

Alternatives to Supabase Storage Search

PostgreSQL Full-Text Search: Store file metadata in your database and search there

Elasticsearch: For large-scale file searches, consider a separate search service

AWS S3 with CloudSearch: If migrating off Supabase

Typesense/MeiliSearch: Self-hosted open-source search alternatives

What NOT to Do

❌ Don't attempt to delete and restore your project again

❌ Don't modify storage permissions while troubleshooting

❌ Don't assume all storage operations are broken (only search affected)

Next Steps

1. Report to Supabase: If not already logged, open a support ticket 2. Apply Workarounds: Implement client-side filtering immediately 3. Monitor Status: Check status page for updates (typically resolved within hours) 4. Document Impact: Track which features depend on storage search

Status

Last Updated: [Current monitoring status] Expected Resolution: Supabase engineering team is actively investigating

For real-time updates, follow [@supabase](https://twitter.com/supabase) and check the official status page.