Vendor reports: operationalResolved · vendor status “resolved”Official status API

Delayed Metric Alert Evaluation | US-East-1

Reported by LogicMonitor · Observability & Incident · source last read 5 min ago

Official source (opens in a new tab)
Vendor start
May 8, 2026, 01:10 UTC
Vendor's clock
Resolved
May 9, 2026, 18:13 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 d 17 h
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

  • LogicMonitor reports operational: "Delayed Metric Alert Evaluation | US-East-1".[E1, E2]
  • The vendor marked it resolved at 2026-05-09 18:13 UTC.[E3, E7]

Affected products and regions

  • Regions: us-east-1 (read from the title, so inferred).[E5]
  • Components: Alert Delivery, Graphing, NetFlow, Time Series Data Ingestion and Persistence, AWS ec2-us-east-1.[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-05-09 18:13 UTC · summary s1, evidence 4f50d59eb6c602c5

Evidence (7)
  1. E1LogicMonitor reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Delayed Metric Alert Evaluation | US-East-1". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-05-08 01:10 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-east-1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: Alert Delivery, Graphing, NetFlow, Time Series Data Ingestion and Persistence, AWS ec2-us-east-1. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-05-09 18:13 UTC. (vendor) source (opens in a new tab)

Affected scope

us-east-1

Components: Alert Delivery, Graphing, NetFlow, Time Series Data Ingestion and Persistence, AWS ec2-us-east-1

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

LogicMonitor 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. May 8, 2026, 01:10 UTCVendor-reported startVendor time
  2. May 9, 2026, 18:13 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.