Where does this status come from?

From Algolia's own status API at https://status.algolia.com. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Algolia's words.

How can my agent or app check Algolia status?

Fetch https://upbutler.com/status/algolia/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"algolia"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Algolia's?

Add "algolia" to the dependencies of your UpButler workspace. When one of your monitors fails while Algolia has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Algolia down?

Right now

Partly. Algolia is degraded.

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

Read from status.algolia.com 3 min ago · every 300s

For agents

proceed

Proceed, expect slow or flaky responses.

GET upbutler.com/status/algolia/status.agent.json

MCP: upstream_status {"service":"algolia"}

Hosted search. Status is per cluster; this page shows the worst cluster and recent cluster incidents.

What Algolia reports

Degraded· 5 open incidents

Taken as is from Algolia's own status API. Incident titles and component names below are theirs.

Open status.algolia.com

UpButler's independent probe

There is no keyless endpoint of Algolia that says anything useful, so UpButler does not probe it. To check your own Algolia account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Algolia

Incident on cluster r20-br: We are encountering a major issue that impact all API calls.investigating · impact minor
Since 2026-10-07 07:57 UTC · r20-br
Incident on cluster r18-in: We are encountering a major issue that impact all API calls.investigating · impact minor
Since 2026-10-07 07:53 UTC · r18-in
Incident on cluster r19-sg: We are encountering a major issue that impact all API calls.investigating · impact minor
Since 2026-10-07 07:52 UTC · r19-sg
Incident on cluster r17-usw: We are encountering a major issue that impact all API calls.investigating · impact minor
Since 2026-10-07 07:51 UTC · r17-usw
Incident on cluster r16-use: We are encountering a major issue that impact all API calls.investigating · impact minor
Since 2026-10-07 07:07 UTC · r16-use

Text written by Algolia, shown unchanged.

Algolia components

5 of 5 not operational

Cluster r16-useMajor outage
Cluster r17-uswMajor outage
Cluster r18-inMajor outage
Cluster r19-sgMajor outage
Cluster r20-brMajor outage

Algolia incidents, last 90 days

1 finished incident seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Algolia.

Started (UTC)	Incident	Impact	Lasted
2026-10-07 09:26	Incident on cluster m435-za: We are encountering issues with add/update API calls. Search queries are not impacted.	major	2 min

Tell your outage from Algolia's

Declare that your project depends on Algolia. When one of your monitors fails while Algolia has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - algolia

Ask before you retry

curl -s https://upbutler.com/status/algolia/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "algolia",
  "verdict": "proceed",
  "status": "degraded",
  "reason": "Incident on cluster r20-br: We are encountering a major issue that impact all API calls.",
  "retryAfterSec": null,
  "incident": {
    "title": "Incident on cluster r20-br: We are encountering a major issue that impact all API calls.",
    "url": "https://status.algolia.com"
  },
  "probe": null
}

Questions

Is Algolia down right now?: Partly. As of 2026-10-10 05:09 UTC, Algolia is degraded, with an open incident: "Incident on cluster r20-br: We are encountering a major issue that impact all API calls.". This page reads the status again every 5 minutes.
Where does this status come from?: From Algolia's own status API at https://status.algolia.com. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Algolia's words.
How can my agent or app check Algolia status?: Fetch https://upbutler.com/status/algolia/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"algolia"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Algolia's?: Add "algolia" to the dependencies of your UpButler workspace. When one of your monitors fails while Algolia has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in search and web data

UpButler is not affiliated with Algolia. Status and incident text belong to Algolia and are read from their public status source; the probe result is UpButler's own measurement.