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

Certificate renewal for Filebeat-based Integrations in us-east-1 and eu-central

Reported by Logz.io · Observability & Incident · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Jul 28, 2025, 09:22 UTC
Vendor's clock
Resolved
Jul 25, 2025, 13:00 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
Needs both vendor times

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Logz.io reports operational: "Certificate renewal for Filebeat-based Integrations in us-east-1 and eu-central".[E1, E2]
  • The vendor marked it resolved at 2025-07-25 13:00 UTC.[E3, E7]

Affected products and regions

  • Regions: us-east-1 (read from the title, so inferred).[E5]

What is unknown

  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-07-28 09:22 UTC · summary s1, evidence fda91a2edd083372

Evidence (7)
  1. E1Logz.io reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Certificate renewal for Filebeat-based Integrations in us-east-1 and eu-central". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-07-28 09:22 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. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2025-07-25 13:00 UTC. (vendor) source (opens in a new tab)

Affected scope

us-east-1

Components: not stated by the vendor

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

Potential relevance

Logz.io 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. Jul 25, 2025, 13:00 UTCVendor-reported resolutionVendor time
  2. Jul 28, 2025, 09:22 UTCVendor-reported startVendor time

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