Marqo outage history

We hold 5 Marqo incidents from Marqo's status page, the newest from Oct 23, 2026. 1 of the 5 listed carry Marqo's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 20d 18h since the last recorded problem.
Operational · 24h
100%
0 incidents · no downtime
288 checks
Operational · 7d
100%
0 incidents · no downtime
2015 checks
Operational · 30d
98.50%
1 incident · ≈10h 50m degraded
8638 checks
Operational · since Jun 22, 2026
99.68%
1 incident · ≈10h 50m degraded
41216 checks

% of our checks that found Marqo fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow
Past incidents

How Marqo fails

Since Oct 23, 2026, Marqo's status page has marked one Marqo component as impaired, across 128 of our five-minute readings. Marqo Cloud Data Plane accounts for the most: 128 readings (about 11 hours) on 1 day, most recently on Oct 23, 2026. We hold 5 Marqo incidents from Marqo's status page, the earliest from Apr 13, 2026.

ComponentOutageDegradedMaint.DaysLast
Marqo Cloud Data Plane—128—1Oct 23, 2026

Incidents by month: Apr 2026: 2 · May 2026: 2 · Oct 2026: 1

Counts are five-minute readings of Marqo's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

Every recorded incident

October 2026 · 1

May 2026 · 2

April 2026 · 2

Incidents and their updates are Marqo's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Marqo.