BREAKING: Supabase Storage Search Failing for Restored Projects

Supabase experiencing storage search functionality issues on restored projects. Immediate workarounds and status inside.

BREAKING: Supabase Storage Search Failing for Restored Projects

What's Down

Subabase is reporting a monitoring-level incident affecting Storage search functionality specifically for restored projects. Users attempting to search or list objects within Supabase Storage buckets on projects that have been restored from backups are experiencing failures.

This appears to be isolated to the search/listing operations rather than core storage read/write functionality.

How to Check If You're Affected

  • Your project was recently restored from a backup
  • You're attempting to search for files or list bucket contents via the Supabase dashboard or API
  • You receive errors when calling storage list/search endpoints
  • The Supabase dashboard Storage tab shows loading errors or returns empty results unexpectedly
  • Check your project status: Visit your Supabase project dashboard and navigate to Storage. Try listing a bucket's contents.

    Immediate Workarounds

    1. Direct File Access (if you know the path)

    If you know the exact file path/name, bypass search functionality: ```javascript const { data, error } = await supabase .storage .from('bucket-name') .download('known-file-path.txt'); ```

    2. Use RLS-Protected Bucket Queries

    Instead of relying on dashboard storage search, query your file metadata from a database table if you're storing file references: ```javascript const { data } = await supabase .from('files') .select('*') .eq('bucket_name', 'your-bucket'); ```

    3. Delay Restore Operations

    If possible, avoid restoring projects until Supabase confirms the issue is resolved. If not urgent, schedule restoration during maintenance windows.

    4. Use Alternative Storage Temporarily

    For time-sensitive operations, consider:
  • AWS S3 (native or via Supabase S3 integration if available)
  • Cloudinary for media files
  • Firebase Storage
  • MinIO or other self-hosted solutions
  • 5. Contact Supabase Support

    File an urgent support ticket with:
  • Project ID
  • Restore timestamp
  • Specific bucket names affected
  • Whether this is blocking production
  • What We Don't Know Yet

  • Exact cause of the storage search failure
  • Percentage of users affected
  • ETA for resolution
  • Whether this affects all restore operations or specific backup restore types
  • Impact on storage write operations (appears unaffected but unconfirmed)
  • Status

    This is a monitoring-level incident. Supabase is actively investigating. Check:

  • [Supabase Status Page](https://status.supabase.com)
  • Your Supabase dashboard notifications
  • Supabase Discord #status channel
  • Recommendations

    1. Do not restore new projects until resolution is confirmed 2. Document your file paths for workaround access 3. Monitor the status page for updates 4. Implement fallback logic in your application to handle search failures gracefully 5. Test your backup strategy with non-critical projects first

    Last Updated: Ongoing - Check official Supabase status for latest information.

    πŸ”₯ 0d
    LIVE
    ↓ PlanetScale rage spiking β€’βš  Vercel pricing complaints ‒↑ Railway gaining fast ‒↑ Supabase happiness rising ‒↑ Resend loved by devs ‒↓ PlanetScale rage spiking β€’βš  Vercel pricing complaints ‒↑ Railway gaining fast ‒↑ Supabase happiness rising
    DEVELOPER PAIN RADAR // Loading...

    Developers complain.
    Opportunities appear.

    We track what developers are struggling with today β€” and what opportunities that creates.

    β€”
    guides today
    β€”
    avg happiness
    πŸ”₯ Pain
    πŸ“– Guides
    πŸ”­ Explore
    πŸ‘€ Mine
    πŸ”₯ Pain Radar β€” rage scores today
    β†— share
    πŸ’‘ Opportunity Feed β€” pain = market gap
    πŸ“ˆ Tool Momentum
    all scores β†’
    πŸ“– Latest Guide
    all guides β†’
    πŸ“– All Guides
    πŸ“Š Tool Scores
    + Submit
    πŸ“° Hacker News
    βž• Submit a Tool
    ← back