rewindex

CompaniesMezmoIncidents

Mezmo: Indexing Delay

No impact listedStatus: resolvedStarted Resolved (6.7 h)1 updatestatus.mezmo.com (opens in new tab)

Timeline of updates

  1. resolved

    The call to retrieve context menu information was silently returning no information. We have since rectified this issue by modifying the API call.

From Mezmo’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.mezmo.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Mezmo, started 2018-05-30 11:00 UTC, resolved after 6.7 h, 1 update(s).

Title
Indexing Delay
Vendor
Mezmo
Date
URL
https://rewindex.com/company/mezmo/incidents/nzkprrwgzcv0

Mezmo profileRecent Mezmo incidentsAll outages on May 30, 2018Mezmo in May 2018MarkdownJSON