Mezmo change history

Mezmo reported major Search and Livetail performance issues in Log Analysis from 2025-09-15 20:18 UTC to 2025-09-15 21:16 UTC, lasting 58 min. Data continued to be ingested, indexed, and retained, but displayed slowly in live tail; Mezmo confirmed Search performance was back to normal at resolution.

Mezmo reported a critical search outage preventing events from displaying in live tail, starting 2025-09-08 19:55 UTC and resolved at 2025-09-08 21:53 UTC, lasting 1 h 57 min. Impacts were mitigated by 21:24 UTC; Mezmo made a backend change it believes should mitigate recurrence, while the underlying cause remained unspecified.

Mezmo reported a major outage preventing customers from viewing logs in Log Analysis - Search, Log Analysis - Web App, Search, and Web App. It started at 2025-03-18 13:33 UTC and was resolved at 2025-03-18 14:29 UTC, lasting 56 min; Mezmo implemented a fix and reported processing lag before recent logs became available.

Mezmo’s critical Pipeline Web UI outage started 2024-10-26 01:00 UTC and resolved 2024-10-26 20:23 UTC (19 h 23 min). Pages failed to load, then loaded slowly with metrics sometimes unavailable; ingress and egress were unaffected. The postmortem limited customer impact to the first four hours; no cause or specific fix was stated.

Mezmo reported a major outage from 2023-08-29 21:01 UTC to 2023-08-30 00:17 UTC, lasting 3 h 16 min. Its Kong Gateway stopped functioning, preventing Web UI access and log ingestion through the agent or API; syslog ingestion was unaffected. The incident was resolved, but no fix was specified.

Mezmo reported a critical Web App outage: the Web UI was inaccessible and returned “failure to get a peer from the ring-balancer.” The incident record started at 2023-05-01 20:18 UTC and was resolved at 2023-05-01 20:27 UTC, lasting 9 min; the postmortem lists a different outage window.

Mezmo reported major Search degradation starting 2023-02-10 18:11 UTC, resolved at 2023-02-10 18:14 UTC (computed duration: 2 min). Searches were slow or returned no results; no data was lost and ingestion continued. The postmortem lists an earlier start of 16:45 UTC; normal search speeds were restored.

Mezmo reported a major degradation affecting Livetail, Search and Web App from 2023-02-06 20:48 UTC to 2023-02-07 02:07 UTC, lasting 5 h 18 min. Searches were slow or returned no results, and the Web UI was intermittently unresponsive; all search data access was restored. No data was lost, and ingestion was not halted.

Mezmo reported a major log-ingestion degradation starting 2022-06-30 21:36 UTC, resolved at 2022-06-30 22:11 UTC (35 min). A downstream parser discarded some customers’ accepted logs, which were not retained; newly submitted logs were processing and being retained at resolution.

Mezmo reported a critical log-ingestion outage across all sources from 2022-06-02 21:44 UTC to 2022-06-02 22:05 UTC (21 min). Newly submitted logs were never ingested, making them unavailable for Alerting, Searching, Live Tail, Graphing, Timelines, and Archiving. Ingestion resumed and all services were fully operational.

Mezmo’s critical Alerting outage ran from 2022-04-05 18:23 UTC to 2022-04-05 18:32 UTC (9 min); alerts failed for all accounts before service resumed. The postmortem mentions a parser service restart and says most alerts with trigger dates more than 15 minutes in the past were discarded.

Mezmo reported major, Syslog-only log ingestion failures from 2022-02-24 22:45 UTC to resolution at 2022-02-24 23:43 UTC (57 min computed). New logs intermittently failed to ingest. The postmortem gives an earlier start—Thursday, February 18, 2022, at 00:10 UTC—and mentions the newly introduced Syslog Forwarder service.

Mezmo reported a major degradation: new-log ingestion through its Syslog endpoint intermittently failed from 2022-02-18 01:41 UTC to 2022-02-18 02:15 UTC (33 min). The incident was resolved; the postmortem attributed the failures to a code change in Syslog Forwarder, which handles Syslog ingestion.

Mezmo reported a major Log Ingestion (Syslog) outage affecting some custom-port logs, making them unavailable for Alerting, Searching, Timelines, Graphs, and Live Tail; logs not using custom ports worked normally. It started at 2022-02-16 19:58 UTC and resolved at 2022-02-16 21:56 UTC (1 h 57 min). A fix was implemented.

Mezmo reported a critical outage: ingestion halted, delaying Searching, Live Tail, Alerting, Graphing, and Timelines; some alerts never triggered. The incident ran from 2022-01-26 16:10 UTC to 2022-01-26 17:15 UTC, lasting 1 h 5 min. A fix restored ingestion and all services by 16:58 UTC.

Mezmo reported a major outage affecting US email alerts and delaying email notifications from 2021-10-28 18:13 UTC to 2021-10-28 23:22 UTC (5 h 9 min). Mezmo attributed it to an incident at email provider Sparkpost; Slack and webhook notifications were unaffected. Email alerting was restored.

Mezmo reported a major Web App outage preventing some customers from logging in or loading pages from 2021-10-07 17:52 UTC to 2021-10-07 18:46 UTC (53 min). Log ingestion was unaffected; the postmortem attributed the disruption to a major network routing outage at Telia in Europe. All services were operational at resolution.

Mezmo reported a major email-alerting outage starting 2021-10-06 21:29 UTC, lasting 1 h 5 min and resolving at 2021-10-06 22:35 UTC; Slack and webhook alerts remained functional. The postmortem attributed partial email-notification disruption to exceeding its email provider’s daily limit of 250,000 messages; email alerting was restored.

Mezmo reported a major incident affecting Web UI searches and Live Tail from 2021-08-19 13:56 UTC to 2021-08-19 20:48 UTC, lasting 6 h 52 min. Intermittent failures affected some customers; about 12% also experienced delays before newly submitted logs were available for searching, graphing, and timelines. Mezmo took remedial action and reported all services fully operational.

Mezmo’s major incident delayed all customers’ logs in the WebUI, Alerting, Live Tail and archive uploads. The postmortem lists the start as April 28, 2021 at 12:37 UTC; resolution was 2021-05-03 00:54 UTC (computed duration: 2 days 12 h). All services were reported fully operational, with archives uploading to their destinations.

Mezmo reported a major Web UI outage affecting Livetail, Search, and Web App; log searches could return errors. It started at 2021-04-23 06:17 UTC and was resolved at 2021-04-23 06:45 UTC, lasting 27 min. Mezmo reported restoring log access and confirmed the Web UI was fully operational.

Mezmo reported a major incident affecting LogDNA’s Web App, Livetail and Search: pages were not loading consistently. It started at 2021-04-20 09:04 UTC and was resolved at 2021-04-20 11:54 UTC, lasting 2 h 50 min. Engineers applied a fix, and logs were accessible in the web app upon resolution.

Mezmo reported a major outage affecting Search, Livetail and the Web App: users could not search logs or use Live Tail in the Web UI. The incident ran from 2021-03-04 08:00 UTC to 2021-03-04 08:21 UTC (21 min); a fix was implemented at 2021-03-04 08:12 UTC.

Mezmo reported a critical outage affecting the Web UI and log ingestion, starting at 2021-01-14 20:05 UTC and resolved at 2021-01-14 20:27 UTC (computed duration: 21 min). All services were restored; the postmortem separately reports 45 minutes of disruption and says ingestion client agent logs were automatically resent and successfully ingested.

Mezmo reported a major Web App outage affecting https://app.logdna.com from 2020-12-16 22:54 UTC to 2020-12-16 23:02 UTC, lasting 8 min. The vendor identified and resolved the issue but did not specify a cause or fix.