Is Algolia Down?

No — Algolia is up

Reachable from all 8 checked regions

Average response time: 834ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://status.algolia.com

Algolia uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

665ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 33 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

33-day clean streak

Aug 12 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

589ms

DNS 0ms TCP 2ms TLS 9ms TTFB 492ms

arn

685ms

DNS 0ms TCP 1ms TLS 6ms TTFB 579ms

bom

982ms

DNS 0ms TCP 2ms TLS 8ms TTFB 682ms

ord

253ms

DNS 0ms TCP 2ms TLS 16ms TTFB 228ms

sin

1436ms

DNS 0ms TCP 1ms TLS 7ms TTFB 1057ms

sjc

283ms

DNS 0ms TCP 2ms TLS 10ms TTFB 205ms

syd

2230ms

DNS 0ms TCP 1ms TLS 6ms TTFB 1924ms

yyz

217ms

DNS 0ms TCP 1ms TLS 11ms TTFB 199ms

What Algolia does

Algolia is a hosted search API. Sites and apps send it their catalogue or content, and it returns ranked results fast enough to update as someone types. It is used for product search, documentation search and in-app search across e-commerce and SaaS. Because it sits inside someone else's page, an Algolia fault usually surfaces as that site's search box breaking.

What an outage looks like

Algolia's status page reports the Search API across 14 regions, plus Analytics, Insights, Dashboard and Usage separately. When the Search API is affected, search boxes return no results, hang, or fall back to an empty state while the rest of the page renders normally. Algolia reports incidents against named clusters, so one customer's index can be affected while others are not.

What to do about it

Check status.algolia.com, which shows daily availability per service and marks how many regions are healthy, then confirm which cluster serves your application. Algolia notes that the dashboard gives personalised status for the specific servers you run on, which the public page cannot. A cluster-scoped incident affects only the applications on it, so the public page reading green is not conclusive.

Is it down for everyone, or just you?

If this page says Algolia is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Cloudflare

AWS

Vercel

MongoDB Atlas

Algolia outage FAQ

Search is broken on a site I use. Is that Algolia?

It can be. Algolia powers the search box on many sites without branding it, so a page that loads normally while search returns nothing is a recognisable pattern. Algolia's status page reports the Search API by region and shows 90-day availability per service. If Algolia is operational, the fault is more likely in how the site queries it or in its index.

What is a cluster incident on Algolia's status page?

Algolia runs customer applications on named clusters and posts incidents against a specific one, such as an issue affecting all API calls on a single cluster. Only applications hosted on that cluster are affected. That is why the top-level status can read as operational while a subset of customers is fully down, and why Algolia points people at their dashboard for a personalised view.

Does an Algolia outage lose my index data?

Indexed records are stored by Algolia and are not deleted by an availability incident. What can be lost is indexing work submitted during the outage: writes that fail need to be resent. If your pipeline pushes updates on a schedule, check that the batch covering the outage window actually applied rather than assuming it retried on its own.

Does Algolia going down affect analytics as well as search?

Not necessarily. Analytics, Insights and Usage are tracked as separate services from the Search API, each with its own regional coverage and availability figures. Search can be fully operational while Insights is degraded, which shows up as missing click and conversion data rather than broken search. The status page lists availability for each over the last 90 days.

How we measure this

We request Algolia's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Algolia publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Algolia goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required