Vendor Status Watch

← all vendors

Logz status history

Current state: operational — “All Systems Operational” per https://status.logz.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

2incidents, last 30 days
5incidents, last 90 days
43incidents on record
Incidents per week, last 12 weeks:

How long do Logz incidents last?

62 minmedian incident duration43 measured
4.3 h90th percentile1 in 10 ran longer
110 minmedian, major/critical only3 incidents

From 43 incidents with a vendor-posted start and resolve time. Longest on record: Ongoing AWS us-east Outage Impacting Metrics and Logs Ingestion — 13.1 h (2025-10-20 07:30 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (43)

StartedIncidentStatusImpactDuration
2026-09-09 15:28 UTCEU-Central-1: Some Customers Experiencing Lagresolvedminor1 h 02 min
2026-08-21 15:29 UTCCanada - Data Ingestions Delays For Some Customersresolvedminor56 min
2026-08-05 23:00 UTCData Ingestions Delays For Some Customers - Degraded Performance - us-east-1resolvednone0 min
2026-07-09 01:05 UTCUS-East - Data Ingestions Delays For Some Customersresolvedminor21 min
2026-07-08 16:51 UTCUS-East - Data Ingestions Delays For Some Customersresolvednone1 h 45 min
2026-06-08 13:21 UTCLogs Ingestions Delays For Some Accounts - Monitoringresolvedminor3 h 18 min
2026-06-08 12:21 UTCUS-EAST-1: Some Customers Experiencing Delayed Metrics Ingestionresolvedminor4 h 19 min
2026-06-04 01:45 UTCLog Ingestions Delays In us-east-1 For Some Accountsresolvednone0 min
2026-05-10 13:30 UTCSome Customers on the EU Central Region are Experiencing Log Shipping Issuesresolvednone0 min
2026-05-08 00:53 UTCUS-East - Data Ingestions Delays Due to AWS outage for Some Customers - Degraded Performanceresolvedminor7 h 09 min
2026-05-06 10:39 UTCOrionIQ Invocations Failures For Some Customersresolvedminor1 h 09 min
2026-04-29 21:34 UTCUS-East - Delayed Alerting for Some Customersresolvedminor2 h 51 min
2026-04-10 16:37 UTCUS-EAST: Delayed indexing in opensearch for some customersresolvedminor1 h 14 min
2026-03-30 13:21 UTCSome Customers Experiencing Lag for Rolled Up Metrics: eu-central-1resolvedminor1 h 09 min
2026-03-27 07:58 UTCDegraded Log Ingestionresolvednone58 min
2026-03-10 19:34 UTCUS-East - Delayed Alerting for Some Customersresolvedminor28 min
2026-03-03 16:16 UTCSome Customers Experiencing Metrics Latency on us-east-1resolvedminor4 h 19 min
2026-03-03 16:02 UTCSome Accounts in AWS US-East Region are Experiencing Alert Delayresolvedminor2 h 45 min
2026-02-26 22:33 UTCA few customers in US-East-1 are experiencing delays with log ingestionresolvednone35 min
2026-02-23 17:38 UTCAWS eu-central-1 - Metrics - Outageresolvednone21 min
2026-02-18 18:59 UTCData Ingestions Delays for Specific Regionsresolvedmajor1 h 50 min
2026-01-29 13:38 UTCAWS ap-northeast-1 - Some customers experiencing log ingestion lagresolvedminor8 min
2026-01-22 02:15 UTCData Ingestions Delays For Some Customers - Degraded Performance - eu-centralresolvedminor3 h 13 min
2026-01-05 19:06 UTCSome Customers Experiencing Degraded Performance for Metricsresolvedminor4 h 53 min
2025-12-18 09:31 UTCData Ingestions Delays For Some Customers - Degraded Performance - eu-centralresolvedminor38 min
2025-12-18 08:00 UTCData Ingestions Delays For Some Customers - Degraded Performance - eu-centralresolvednone0 min
2025-12-13 13:54 UTCData Ingestions Delays For TRIAL Customers - Degraded Performance - Identified - us-east-1resolvedminor34 min
2025-12-09 09:11 UTCData Ingestions Delays - For Few Customers in en-central-1 - Degraded Performance - Monitoringresolvedminor1 h 35 min
2025-12-04 12:45 UTCSome Customers In us-east-1 Are Experiencing Data Ingestions Delays - Degraded Performance - Identifiedresolvedminor39 min
2025-12-02 20:58 UTCData Ingestions Delays for Some Customers in the US East Regionresolvedminor1 h 16 min
2025-11-25 12:00 UTCData Ingestions Delays For Some Customers In eu-west-2resolvedminor21 min
2025-11-18 14:29 UTCA few customers in US-East-1 are experiencing delays with logs ingestionresolvednone22 min
2025-11-14 15:57 UTCA few customers in US-East-1 are experiencing delays with logs and metrics ingestionresolvednone1 h 25 min
2025-10-22 13:41 UTCLog Ingestion Delays In US-East-1 For Some Customersresolvedminor1 h 11 min
2025-10-22 11:15 UTCDelay In Metric ingestion For Some Customers In us-east-1resolvedminor39 min
2025-10-20 07:30 UTCOngoing AWS us-east Outage Impacting Metrics and Logs Ingestionresolvednone13 h 07 min
2025-10-16 11:23 UTCPartial Dashboard Metrics Degradation Performanceresolvedminor32 min
2025-10-10 00:04 UTCDegraded Metrics Ingestion for Eu-Central-1resolvedminor30 min
2025-09-30 22:01 UTCUS-EAST: Some customers are experiencing an issue when accessing Grafana UIresolvedcritical2 h 04 min
2025-09-25 11:02 UTCPartial – Some customers may see delayed metrics ingestionresolvedminor48 min
2025-09-16 01:14 UTCus-east-1 - Metrics Ingestion - Inconsistent Ingestionresolvedmajor53 min
2025-09-03 10:46 UTCA few Accounts in AWS US-East Region are Experiencing Degradation on loading Metrics Tabresolvedminor3 h 17 min
2025-08-24 21:04 UTCSome Accounts in AWS US-East Region are Experiencing Log Ingestion Lagresolvedminor4 h 46 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Logz with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "logz"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}