Unexpected errors returned by Meilisearch

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 27m it lasted.

  Anything that failed between 2025-11-25 14:57 UTC and 2025-11-25 15:24 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

1. updateNov 25, 2025, 2:57 PM UTC

   We are currently investigating an increased amount of error messages returned by Meilisearch.

   provider

2. updateNov 25, 2025, 3:17 PM UTC

   The issues seems to only occur when using the edge.meilisearch.com. If possible, we advise customers to use their project URL instead to mitigate the issue. We continue to investigate the root cause.

   provider

3. updateNov 25, 2025, 3:22 PM UTC

   We have identified a potential cause in Cloudflare. Our metrics indicate that the error rate is going down. We keep on monitoring to validate that the situation is fixed for all project.

   provider

4. resolvedNov 25, 2025, 3:24 PM UTC

   The issue has been resolved. Our monitors indicate that the situation is back to normal. This issue was caused by a configuration change on our side. It was intended to be fully transparent to customers and only to add security measures to mitigate bot-related traffic. Unfortunately, contrary to our expectations, it affected some users. We have reverted the change and are working with Cloudflare to understand why it was not seamless and how to provide the same level of protection without any negative impact.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.