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

Some logs submitted over syslog using custom ports are not being correctly formatted and are not available for Alerting, Searching, Timelines, Graphs, and Live Tail.

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

Official source (opens in a new tab)
Vendor start
Feb 16, 2022, 19:58 UTC
Vendor's clock
Resolved
Feb 16, 2022, 21:56 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 03:40 UTC
Statuswall's clock
Duration
1 h 58 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 partial outage: "Some logs submitted over syslog using custom ports are not being correctly formatted and are not available for Alerting, Searching, Timelines, Graphs, and Live Tail.".[E1, E2]
  • The vendor marked it resolved at 2022-02-16 21:56 UTC.[E3, E7]

Affected products and regions

  • Components: 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 0d750e2bcdf33053

Evidence (8)
  1. E1Mezmo reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Some logs submitted over syslog using custom ports are not being correctly formatted and are not available for Alerting, Searching, Timelines, Graphs, and Live Tail.". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "postmortem". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2022-02-16 19:58 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 (Syslog). (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2022-02-16 21:56 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 (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. Feb 16, 2022, 19:58 UTCVendor-reported startVendor time
  2. Feb 16, 2022, 21:56 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 03:40 UTCFirst seen by Statuswall (vendor status: postmortem)Seen by Statuswall