- Level
- confirmed
- Worst impact
- Partial outage
What to do
Check whether your product depends on Meilisearch Cloud. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 16m it lasted.
Anything that failed between 2026-07-24 11:02 UTC and 2026-07-24 11:18 UTC may need a replay.Subscribe to Meilisearch Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=meilisearch works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Meilisearch Cloud 4
- update
We are currently investigating issues with our region in San Francisco. Instances are reporting elevated error rate.
provider
- update
Instances appear to be slowly recovering. We are investigating issues related to our cloud provider.
provider
- update
San Francisco instances are now recovering or back online. We are still monitoring the situation.
provider
- resolved
All San Francisco instances are now back online.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-ba0efe285e
Is Meilisearch Cloud still down?
No, this incident was resolved 2026-07-24 11:18 UTC. For Meilisearch Cloud's live state, see https://down.guide/meilisearch.
How long did it last?
16m, from 2026-07-24 11:02 UTC to 2026-07-24 11:18 UTC, by the times Meilisearch Cloud posted.
What caused it?
Meilisearch Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Meilisearch Cloud's official status page, https://status.meilisearch.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.