Meilisearch Cloud Outage History

17 incidents recorded over the last 365 days, 17 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Meilisearch Cloud status99.95% uptime history

Every Recorded Meilisearch Cloud Incident

Meilisearch Cloud incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 18, 2026FRA infrastructure maintenance.2h 0mResolved
Nov 17, 2026NYC infrastructure maintenance1h 30mResolved
Nov 17, 2026LON infrastructure maintenance1h 0mResolved
Nov 17, 2026PAR infrastructure maintenance1h 0mResolved
Nov 16, 2026JPN infrastructure maintenance1h 0mResolved
Nov 16, 2026SYD infrastructure maintenance1h 0mResolved
Nov 16, 2026SFO infrastructure maintenance1h 0mResolved
Nov 16, 2026SAO infrastructure maintenance1h 0mResolved
Nov 16, 2026SGP infrastructure maintenance1h 0mResolved
Jul 24, 2026San Francisco region is experiencing instability1644h 52mResolved
Jul 7, 2026Meilisearch Cloud UI maintenance1h 0mResolved
Jun 24, 2026FRA infrastructure maintenance.2h 0mResolved
Jun 23, 2026SFO infrastructure maintenance1h 0mResolved
Jun 23, 2026NYC infrastructure maintenance2h 0mResolved
Jun 23, 2026LON infrastructure maintenance1h 0mResolved
Jun 22, 2026SGP infrastructure maintenance1h 0mResolved
Jun 22, 2026JPN infrastructure maintenance1h 0mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Meilisearch Cloud incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Meilisearch Cloud Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Meilisearch Cloud acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Meilisearch Cloud outage in this window ran 68d 12h, against a mean recovery of 4d 1h. If you depend on Meilisearch Cloud in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.