- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- eu
What to do
Check whether you use Meilisearch Cloud in eu. 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 1d 3h it lasted.
Anything that failed between 2026-03-25 10:24 UTC and 2026-03-26 14:21 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 7
- update
We are aware of SSL errors in Frankfurt, we are investigating the issue.
provider
- update
We are still investigating the cause of the instance access issues in Frankfurt
provider
- update
We are continuing to investigate an ongoing issue affecting the Frankfurt cluster. The issue has been narrowed to Kong configuration. Our team is actively working on a resolution and we will provide an update as soon as we have more information. We apologize for any disruption this incident is causing.
provider
- update
We are still actively investigating the issue affecting the Frankfurt cluster. Our team has been working through multiple avenues to identify a solution and is continuing to do so with urgency. We will share another update as soon as we have more information. Thank you for your patience and apologies for the disruption caused.
provider
- update
The issue affecting the Frankfurt cluster has been resolved. Instances are coming back online and service is being restored. We will continue to monitor the situation to ensure stability. We appreciate your patience throughout this incident and apologize again for any disruption caused.
provider
- update
All instances in the Frankfurt cluster are back online and operating normally. We will continue monitoring to ensure stability. Thank you for your patience during this incident.
provider
- resolved
Following the incident on Frankfurt, we want to share with you the post-mortem and the next steps we're taking. https://meilisearch.notion.site/2026-03-25-Frankfurt-cluster-incident-report-Kong-failure-32f4b06b651f809c83d4fde9fd7d27e2 We sincerely apologize for any disruption this incident has caused.
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-a1402b49f9
Is Meilisearch Cloud still down?
No, this incident was resolved 2026-03-26 14:21 UTC. For Meilisearch Cloud's live state, see https://down.guide/meilisearch.
How long did it last?
1d 3h, from 2026-03-25 10:24 UTC to 2026-03-26 14:21 UTC, by the times Meilisearch Cloud posted.
What was affected?
Meilisearch Cloud named in eu.
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.