Vendor reports: major outageResolved · vendor status “postmortem”Official status API

Log lines not ingested

Reported by Mezmo · Observability & Incident · source last read just now

Official source (opens in a new tab)
Vendor start
Jun 2, 2022, 21:44 UTC
Vendor's clock
Resolved
Jun 2, 2022, 22:05 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 03:40 UTC
Statuswall's clock
Duration
21 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Mezmo reports major outage: "Log lines not ingested".[E1, E2]
  • The vendor marked it resolved at 2022-06-02 22:05 UTC.[E3, E7]

Affected products and regions

  • Components: Log Ingestion (Agent/REST API/Code Libraries), Log Ingestion (Heroku), Log Ingestion (Syslog).[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-11 03:40 UTC · summary s1, evidence 0ba68536f2cca4a0

Evidence (8)
  1. E1Mezmo reports major outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Log lines not ingested". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "postmortem". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2022-06-02 21:44 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Log Ingestion (Agent/REST API/Code Libraries), Log Ingestion (Heroku), Log Ingestion (Syslog). (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2022-06-02 22:05 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 03:40 UTC. (Statuswall)

Affected scope

Not stated by the vendor

Components: Log Ingestion (Agent/REST API/Code Libraries), Log Ingestion (Heroku), Log Ingestion (Syslog)

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Mezmo is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jun 2, 2022, 21:44 UTCVendor-reported startVendor time
  2. Jun 2, 2022, 22:05 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 03:40 UTCFirst seen by Statuswall (vendor status: postmortem)Seen by Statuswall
Mezmo: Log lines not ingested — statuswall