Algolia Outage History

49 incidents recorded over the last 365 days, 49 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Algolia status96.65% uptime history

Every Recorded Algolia Incident

Algolia incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 20, 2026Incident on cluster c23-uswWe are encountering a major issue that impact all API calls (liveness check).2 minResolved
Aug 19, 2026Incident on cluster c23-uswWe are encountering a major issue that impact all API calls (liveness check).1 minResolved
Aug 17, 2026Incident on DashboardDashboard is encountering a major outage1 minResolved
Aug 17, 2026Incident on cluster c3-brWe are encountering a major issue that impact all API calls (liveness check).1 minResolved
Aug 10, 2026Incident on cluster c23-uswWe are encountering a major issue that impact all API calls (liveness check).2 minResolved
Aug 6, 2026Incident on cluster c23-uswWe are encountering a major issue that impact all API calls (liveness check).5 minResolved
Aug 4, 2026Incident on cluster c7-euWe are encountering issues with add/update API calls. Search queries are not impacted.4h 48mResolved
Aug 2, 2026Incident on DashboardDashboard is encountering a major outage1 minResolved
Jul 29, 2026Incident on cluster s8-hkWe are encountering a major issue that impact all API calls (liveness check).0 minResolved
Jul 24, 2026Incident on cluster c23-uswWe are encountering a major issue that impact all API calls (liveness check).2 minResolved
Jul 22, 2026Incident on cluster m251-useWe are encountering issues with add/update API calls. Search queries are not impacted.1 minResolved
Jul 17, 2026Incident on cluster c9-uscWe are encountering a major issue that impact all API calls (liveness check).0 minResolved
Jul 15, 2026Incident on cluster s5-deWe are encountering a major issue that impact all API calls (liveness check).1h 11mResolved
Jun 18, 2026Incident impacting the CrawlerWe have an ongoing incident impacting the Crawler. Our Engineering team is actively investigating the issue.1108h 2mResolved
Jun 15, 2026Incident on cluster s5-uaeWe are encountering a major issue that impact all API calls.3 minResolved
Jun 15, 2026Incident on cluster s6-uswWe are encountering a major issue that impact all API calls (liveness check).4 minResolved
Jun 15, 2026Incident on cluster s9-auWe are encountering a major issue that impact all API calls (liveness check).1h 13mResolved
Jun 15, 2026Incident on cluster s9-hkWe are encountering a major issue that impact all API calls (liveness check).3 minResolved
Jun 15, 2026Incident on cluster s12-inWe are encountering a major issue that impact all API calls (liveness check).2 minResolved
Jun 15, 2026Incident on cluster s11-zaWe are encountering a major issue that impact all API calls (liveness check).4 minResolved
Jun 15, 2026Incident on cluster s5-uswWe are encountering a major issue that impact all API calls (liveness check).3 minResolved
Jun 15, 2026Incident on cluster s4-ukWe are encountering a major issue that impact all API calls (liveness check).3 minResolved
Jun 15, 2026Incident on cluster s5-sgWe are encountering a major issue that impact all API calls (liveness check).0 minResolved
Jun 15, 2026Incident on cluster s16-jpWe are encountering a major issue that impact all API calls (liveness check).2 minResolved
Jun 15, 2026Incident on cluster s8-hkWe are encountering a major issue that impact all API calls (liveness check).3 minResolved
Jun 15, 2026Incident on cluster s9-euWe are encountering a major issue that impact all API calls (liveness check).1 minResolved
Jun 15, 2026Incident on cluster s5-deWe are encountering a major issue that impact all API calls (liveness check).2 minResolved
Jun 15, 2026Incident on cluster s8-auWe are encountering a major issue that impact all API calls (liveness check).1h 12mResolved
Jun 15, 2026Incident on cluster s17-brWe are encountering a major issue that impact all API calls (liveness check).1 minResolved
Jun 15, 2026Incident on cluster s8-caWe are encountering a major issue that impact all API calls.4 minResolved
Jun 15, 2026Incident on cluster s11-useWe are encountering a major issue that impact all API calls (liveness check).2 minResolved
Jun 15, 2026Incident on cluster s10-useWe are encountering a major issue that impact all API calls (liveness check).2 minResolved
Jun 3, 2026Issue with Shopify affecting users of our Shopify ExtensionUsers of our Shopify integration may be encountering issues due to an issue with Shopify. You can find more details of the issue here: https://www.shopifystatus.com/1467h 50mResolved
Jun 3, 2026Issue with Shopify affecting users of our Shopify ExtensionUsers of our Shopify integration may be encountering issues due to an issue with Shopify. You can find more details of the issue here: https://www.shopifystatus.com/15h 15mResolved
May 19, 2026Incident on Insights USInsights US is encountering a major outage1831h 5mResolved
May 19, 2026Incident on Insights DEInsights DE is encountering a major outage1831h 5mResolved
May 19, 2026Incident on UsageUsage API is encountering a major outage1831h 5mResolved
May 4, 2026Incident on cluster m251-useWe are encountering a major issue that impact all API calls.2194h 14mResolved
May 4, 2026Incident on cluster m232-euWe are encountering a major issue that impact all API calls.2194h 14mResolved
May 4, 2026Incident on cluster m245-ukWe are encountering a major issue that impact all API calls.2194h 14mResolved
May 4, 2026Incident on cluster m250-jpWe are encountering a major issue that impact all API calls.2194h 14mResolved
May 4, 2026Incident on cluster m93-auWe are encountering a major issue that impact all API calls.2194h 14mResolved
May 4, 2026Incident on cluster m249-caWe are encountering a major issue that impact all API calls.2194h 14mResolved
May 4, 2026Incident on cluster m252-uswWe are encountering a major issue that impact all API calls.2194h 14mResolved
May 4, 2026Incident on cluster m242-deWe are encountering a major issue that impact all API calls.2194h 14mResolved
May 4, 2026Incident on cluster m81-uscWe are encountering a major issue that impact all API calls.2194h 14mResolved
May 3, 2026Incident on cluster m250-jpWe are encountering issues with add/update API calls. Search queries are not impacted.2217h 36mResolved
Apr 23, 2026Incident on cluster c32-euWe are encountering a major issue that impact all API calls (liveness check).2452h 7mResolved
Apr 22, 2026Indexing outage on BigCommerce integrationThere is an ongoing incident affecting indexing functionality in our BigCommerce integration. Additionally, the BigCommerce app is currently non-functional. Our engineering team is investigating the issue. Search…2481h 40mResolved

How to Read This Algolia Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Algolia acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Algolia outage in this window ran 103d 9h, against a mean recovery of 29d 18h. If you depend on Algolia in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.