←View full LanceDB Cloud status
LanceDB Cloud: Index / Collection Unavailable
Current Status: Operational
Last checked: 3m ago
What We're Seeing Right Now
No recent issues reported. If you're experiencing problems with LanceDB Cloud, report below to help the community.
What is this error?
Your vector index or collection on LanceDB Cloud is returning errors or appears to be missing. This can happen after index recreation, namespace issues, or platform-side storage problems.
Error Signatures
Index not foundCollection does not existNamespace not foundIndex is not readyIndex initializingNo such indexResource not foundCommon Causes
- Index was accidentally deleted or recreated with a different name
- Namespace or collection name mismatch in your application code
- Index still initializing after creation or migration
- Platform-side index replication failure
- Account or project permissions changed, revoking index access
✓ How to Fix It
- List all indexes/collections via the LanceDB Cloud API to confirm they exist
- Double-check the index name and namespace in your application configuration
- Verify your API key has read/write access to the target index
- Check if the index shows as 'ready' or 'initializing' in the dashboard
- If the index is missing, check deletion logs in your LanceDB Cloud audit trail
- Contact support if the index disappeared without any action on your end
Live Signals
Service Components
LanceDB Cloud Web
OperationalRecent Incidents
No incidents in the past 30 days
Frequently Asked Questions
Can I recover a deleted vector index on LanceDB Cloud?
Most vector databases do not support point-in-time recovery of deleted indexes. If you have your source data and embeddings generation pipeline, you can re-index. This is why maintaining a source-of-truth dataset is critical.
How long does a new index take to become available on LanceDB Cloud?
Index initialization typically takes seconds to a few minutes for empty indexes. For indexes with millions of vectors, it can take longer. Check the index status via the API before sending queries.
How do I prevent accidental index deletion?
Use LanceDB Cloud's project-level permissions to restrict deletion rights. Add index deletion confirmation to your deployment scripts. Keep a backup of your vector data in your own storage.