CheckUpstream measured Algolia at 100.000% availability across 2830 independent checks (global · api). 27 incidents were recorded in the past 12 months; the most recent resolved 12 days ago after 10 minutes. Status signals are polled from Algolia's official status feed, alongside independent probes and community reports.
90 days measured availability how this is computed
100.000%
global · api · n=2830 · p95 433ms (30d)
Share of our own checks against Algolia endpoints that returned Algolia's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 13 incidents · 90 of 90 days with none posted · 6m of declared impact
Fewer incidents in the last 30 days than 25% of 232 tracked services.
Share of each window with no impact declared by Algolia
7d
100.000%
30d
99.986%
90d
99.995%
180d
99.991%
1y
99.995%
Downtime like this can be refundable
If you're a paying Algolia customer, outages in these windows may count against Algolia's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Algolia entitlement →Does Algolia actually matter to you?
A Algolia outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 13 incidents Algolia published and resolved in the last 90 days, measured between their own start and resolution times. It describes how long Algolia takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 19, 16:00 UTC · resolved in 9m · Resolved
Aug 6, 15:59 UTC · resolved in 10m · Resolved
Aug 4, 10:02 UTC · resolved in 4h 58m · Resolved
Live Algolia status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/algolia)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Algolia is currently Operational. CheckUpstream tracks Algolia in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Algolia's last resolved incident started 12 days ago and lasted 9 minutes (degraded performance).
Looking for the live "is Algolia down" view? See the Algolia Live status page.
Jul 15, 22:13 UTC · resolved in 1h 16m · Resolved
Jun 15, 15:28 UTC · resolved in 1h 17m · Resolved
Jun 15, 15:17 UTC · resolved in 13m · Resolved
Jun 15, 09:49 UTC · resolved in 11m · Resolved
May 14, 14:08 UTC · resolved in 6m · Resolved
May 4, 17:58 UTC · resolved in 11m · Resolved
May 4, 10:09 UTC · resolved in 10m · Resolved
May 4, 09:45 UTC · resolved in 15m · Resolved
May 4, 09:44 UTC · resolved in 15m · Resolved
May 4, 09:44 UTC · resolved in 15m · Resolved
May 4, 09:44 UTC · resolved in 16m · Resolved
Algolia's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Algolia endpoints. It is the share of checks that returned the expected response, not a figure taken from Algolia's status page.
Sign up to CheckUpstream and add Algolia to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Algolia's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.