Mezmo outage, 26 February 2022

Ingestion of new logs to our Syslog endpoint - for logs sent using a custom port, only - is intermittently delayed

Started
Resolved
28 Feb 2022, 18:58 UTC (after 47 h 6 min)
Impact
Not stated
Affected
Log Ingestion (Syslog)

Last update from Mezmo

**Dates:** Start Time: Saturday, February 26, 2022, at 19:51 UTC End Time: Sunday, February 27, 2022, at 22:13 UTC Duration: 26:22:00 ‌ **What happened:** Ingestion of new logs to our Syslog endpoint - for logs sent using a custom port, only - was intermittently delayed. ‌ **Why it happened:** We recently introduced a new service \(Syslog Forwarder\) to handle the ingestion of logs sent over Syslog. As the name implies, it forwards logs to downstream services. Logs are sent from a range of ports on Syslog Forwarder to a range of ports used by clients running on downstream services. This design worked well in our advance testing, using a limited number of custom ports. On...

1 Mar 2022, 20:35 UTC

Read the full incident on the official Mezmo status page

Is Mezmo down now?

This page is the record of one past incident. For the live status, see Is Mezmo down right now? - it reads the official status page every 2 minutes.

Other Mezmo incidents

  1. Impact of AWS Issues

  2. Search performance issues

  3. Problems with Search

  4. Issue with Search

  5. Intermittent issues

  6. Log availability and search performance temporarily degraded

  7. Issues accessing logs in boards and screens

  8. Intermittent Pipeline Service Degradation

All recorded Mezmo incidents