outages.live
Live
AlgoliaIncident · 2026-11-02 09:38 UTC

Incident on cluster m357-eu

ResolvedOfficial update
0

State

Resolved

Started

2 h ago

2026-11-02 09:38 UTC

Lasted

1 min

until 2026-11-02 09:39 UTC

Worst impact

Major outage

Timeline

2 updates
09:3809:3809:3909:3909:39
Major outageUpdate postedTimes in UTC

Major outage

1 min 93%

Operational

1 min 7%

Updates

Times in UTC

As posted by Algolia

Operational2026-11-02 09:39 UTC
Major outage2026-11-02 09:38 UTC

Affected components

1
Search API

Algolia in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

6

Days with an incident

1

Median duration

2 min

This incident

38% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

5 min
median 2 min
90 days agoToday

Other Algolia incidents

All incidents

Algolia·Incident on cluster m358-use

The Algolia Search API does not work for the cluster m358-use. Algolia reports that the incident is resolved. The outage lasted 5 minutes.

Resolvedresolved 2 h ago

Algolia·Incident on cluster m357-eu

The Search API on cluster m357-eu did not work. Algolia reports that the incident is resolved. The outage lasted about 2 minutes.

Resolvedresolved 2 h ago

Algolia·Incident on cluster m249-ca

Algolia reports that cluster m249-ca does not work and affects the Search API. Algolia resolved the outage. The outage lasted 2 minutes.

Resolvedresolved 2 h ago

Algolia·Incident on cluster r17-usw

The Search API did not work on cluster r17-usw. Algolia reports that the incident is resolved. The outage lasted 1 minute.

Resolvedresolved 2 h ago

Algolia·Incident on cluster r18-in

Algolia reports a major outage on the Search API on cluster r18-in. The incident is resolved. It lasted about 1 minute, from 09:40 to 09:41 UTC on 2 November 2026.

Resolvedresolved 2 h ago

Follow Algolia

Your coding agent knows when Algolia is down, and tells you when a failure is theirs, not yours. You can also get Algolia incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "algolia" and tell me if Algolia has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=algolia
Slack
/feed subscribe https://outages.cc/feed.xml?providers=algolia

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane