Mezmo status history
Current state: operational — “All Systems Operational” per https://status.mezmo.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Mezmo incidents last?
From 4 incidents with a vendor-posted start and resolve time. Longest on record: Impact of AWS Issues — 9.1 h (2025-10-20 17:00 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (4)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2025-10-20 17:00 UTC | Impact of AWS Issues | resolved | minor | 9 h 07 min |
| 2025-09-15 20:18 UTC | Search performance issues | resolved | major | 58 min |
| 2025-09-09 20:49 UTC | Problems with Search | resolved | none | 3 h 03 min |
| 2025-09-08 19:55 UTC | Issue with Search | resolved | critical | 1 h 57 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Mezmo with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"mezmo"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
