Is Meilisearch down? User reports show no current problems with Meilisearch

Is Meilisearch Down Right Now?

Short answer: if your search stopped working, the problem is usually your own instance, not a global event. Meilisearch runs on your server, so a Meilisearch outage almost always starts at home.

This page tracks the live Meilisearch status through reports from developers and teams. When many users report the same failure at once, it can point to a Meilisearch Cloud problem or a bad release.

Below you will find the faults people hit most often, what each error means, and the checks that fix them. Start with the health endpoint before you change anything else.

Is Meilisearch Down for Me or Everyone?

Ask this first: is Meilisearch down for me, or is it down for everyone running it? The answer decides whether you debug your server or wait for a fix.

Open a terminal and request the /health route on your instance. If it answers with status available, the engine is alive and your app, key, or network is at fault.

If the health check fails too, restart the service and read the startup logs. A Meilisearch down report that starts right after an upgrade often means a version or data file clash.

Why Does Meilisearch Say Invalid API Key?

The invalid_api_key error is the most common Meilisearch complaint by far. It means the key your app sent does not match any key the server expects.

This often happens after a restart with a new master key. Changing the master key changes every API key at once, so old keys in your app config stop working instantly.

Fetch the current keys from the /keys route with your master key. Then update your app, and remember that search keys can only search, never write or create indexes.

Why Are My Meilisearch Tasks Stuck in the Queue?

Every write in Meilisearch becomes a task, and tasks run one batch at a time. A huge import can keep the queue busy and make new changes look frozen.

Check the /tasks route to see the queue. If one task shows failed, read its error field first, since later tasks may be fine once that file is fixed.

Failed tasks often come from a document that breaks index settings, like a wrong primary key. Fix the document, cancel the stuck batch if needed, and send the data again in smaller chunks.

Common Meilisearch Problems and Fixes

Connection Refused on Port 7700

Meilisearch listens on port 7700 by default. A refused connection means the process is not running, crashed at startup, or a firewall blocks the port. Start the binary again and watch the first log lines for the real cause.

Index Not Found Errors

The index_not_found error means your app asked for an index that does not exist. List indexes through the /indexes route and compare names. Index UIDs are case sensitive, so one wrong letter breaks every request.

Search Returns No Results After an Update

New ranking rules or filter settings can empty a result set fast. After an upgrade, check your searchable and filterable attributes. If results still look wrong, rebuild the index from scratch with fresh documents.

Dump Import Fails on a New Version

Dumps must match the version rules of the new server. A dump from a much older release can fail or import half your data. Upgrade in steps, or export documents and reindex them cleanly instead.

Meilisearch Cloud Dashboard Will Not Load

If the cloud dashboard spins forever, sign out and back in, then try a private window. Check reports on this page too. A wider Meilisearch Cloud outage will show many fresh reports within minutes.