Skip to main content

Algolia vs Meilisearch

Front door check counts, what each vendor’s status page recorded and SLA terms for these vendors.

30-day window ending

Front door checks

Every 15 minutes we send a request to a documented endpoint for each vendor from a single CheckUpstream location and count the answers. A reachable front door does not confirm that a customer action worked.

Front door check counts: Algolia and Meilisearch
Last 30 daysAlgoliaMeilisearch
Front door reachableOut of checks with a clear answer
  • 2,879 of 2,879

    checks to status.algolia.com

  • 2,879 of 2,879

    checks to api.meilisearch.com

Checks 15 minutes apart cannot see disruptions shorter than that. Each vendor is checked at its own endpoints, so the counts cover different things.

Algolia · check scope

  • status.algolia.comapi · No vendor region

    Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    First check in this window
    Latest clear answer
View Algolia record

Meilisearch · check scope

  • api.meilisearch.comapi · No vendor region

    Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    First check in this window
    Latest clear answer
View Meilisearch record

What each vendor’s status page says

Recorded starts in the same 30-day window, excluding maintenance. Vendors report incidents differently; fewer posts don’t prove better reliability.

Recorded incidents: Algolia and Meilisearch
Last 30 daysAlgoliaMeilisearch
Incidents recorded

9

0

Recorded incident durationMedian

6d 12h

9 valid durations

Too few dated records

0 valid durations

Duration uses at least 5 incidents with vendor-supplied starts and recorded closure times. First-observed starts are excluded. A record may close when a post disappears or our tracking period expires; this does not confirm recovery. A missing closure time does not mean an outage is ongoing.

Algolia says

  • Incident on cluster r20-br: We are encountering a major issue that impact all API calls.

    Started
    Closed in record
    Source incident
  • Incident on cluster r18-in: We are encountering a major issue that impact all API calls.

    Started
    Closed in record
    Source incident
  • Incident on cluster r18-in: We are encountering a major issue that impact all API calls.

    Started
    Closed in record
    Source incident

Meilisearch says

No incidents recorded in this window. That does not establish an incident-free month.

Check the terms for your plan

An SLA applies to specific products and plans. Credit eligibility also depends on exclusions, evidence and filing deadlines.

Algolia

No public terms recorded here.

Review Algolia SLA guide

Meilisearch

No public terms recorded here.

Review Meilisearch SLA guide