Skip to main content
Vendor reliability

Vendor record

Algolia

Vendor reports Operational

Checked

Front door check counts and Algolia’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Algolia endpoint and count the checks that got the answer it is documented to give.

  • 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.

    Endpoint checked
    status.algolia.com
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Algolia product, region or your app worked.

How we count front door checks

Algolia says

Incident posts from Algolia’s status page, with its titles, impact levels and times. They say what Algolia chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

12

incidents Algolia posted, last 90 days

Median recorded duration: 6d 11h. From 12 incidents with vendor-supplied starts and recorded closure times.

All vendors’ incidents

Most recent records · all dates

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

    Minor

    Started, per Algolia

    Closed in our record(6d 11h)

    Algolia’s post

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

    Minor

    Started, per Algolia

    Closed in our record(6d 11h)

    Algolia’s post

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

    Minor

    Started, per Algolia

    Closed in our record(7d 7h)

    Algolia’s post

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

    Minor

    Started, per Algolia

    Closed in our record(6d 11h)

    Algolia’s post

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

    Minor

    Started, per Algolia

    Closed in our record(7d 7h)

    Algolia’s post
15 older records

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

    Minor

    Started, per Algolia

    Closed in our record(6d 11h)

    Algolia’s post

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

    Minor

    Started, per Algolia

    Closed in our record(7d 7h)

    Algolia’s post

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

    Minor

    Started, per Algolia

    Closed in our record(6d 12h)

    Algolia’s post

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

    Minor

    Started, per Algolia

    Closed in our record(7d 8h)

    Algolia’s post

  • Incident on cluster c23-usw: We are encountering a major issue that impact all API calls (liveness check).

    Minor

    Started, per Algolia

    Closed in our record(9m)

    Algolia’s post

  • Incident on cluster c23-usw: We are encountering a major issue that impact all API calls (liveness check).

    Minor

    Started, per Algolia

    Closed in our record(10m)

    Algolia’s post

  • Incident on cluster c7-eu: We are encountering issues with add/update API calls. Search queries are not impacted.

    Minor

    Started, per Algolia

    Closed in our record(4h 58m)

    Algolia’s post

  • Incident on cluster s5-de: We are encountering a major issue that impact all API calls (liveness check).

    Minor

    Started, per Algolia

    Closed in our record(1h 16m)

    Algolia’s post

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

    Minor

    Started, per Algolia

    Closed in our record(11m)

    Algolia’s post

  • Incident on cluster s6-usw: We are encountering a major issue that impact all API calls (liveness check).

    Minor

    Started, per Algolia

    Closed in our record(7m)

    Algolia’s post

  • Incident on cluster s9-au: We are encountering a major issue that impact all API calls (liveness check).

    Minor

    Started, per Algolia

    Closed in our record(1h 19m)

    Algolia’s post

  • Incident on cluster s11-za: We are encountering a major issue that impact all API calls (liveness check).

    Minor

    Started, per Algolia

    Closed in our record(6m)

    Algolia’s post

  • Incident on cluster s4-uk: We are encountering a major issue that impact all API calls (liveness check).

    Minor

    Started, per Algolia

    Closed in our record(13m)

    Algolia’s post

  • Incident on cluster s16-jp: We are encountering a major issue that impact all API calls (liveness check).

    Minor

    Started, per Algolia

    Closed in our record(10m)

    Algolia’s post

  • Incident on cluster s8-au: We are encountering a major issue that impact all API calls (liveness check).

    Minor

    Started, per Algolia

    Closed in our record(1h 17m)

    Algolia’s post

Your code, your dependencies

See which of your code paths call Algolia

Connect GitHub or GitLab to find where your public or private repository uses Algolia. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Algolia status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · AlgoliaStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/algolia?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Algolia status badge"></iframe>

Frequently Asked Questions

Is Algolia currently down?

Algolia's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Algolia last have an outage?

The most recent closed incident record began 9 days ago and spans 7d 8h. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Algolia?

No. CheckUpstream checks Algolia’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Algolia in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Algolia?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.

Related vendors