Vendor reports: partial outageResolved · vendor status “resolved”Official status API

Account usage data missing

Reported by Loggly · Observability & Incident · source last read just now

Official source (opens in a new tab)
Vendor start
Jul 24, 2024, 16:56 UTC
Vendor's clock
Resolved
Jul 25, 2024, 13:32 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
20 h 36 min
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

  • Loggly reports partial outage: "Account usage data missing".[E1, E2]
  • The vendor marked it resolved at 2024-07-25 13:32 UTC.[E3, E7]

Affected products and regions

  • Components: Account Usage.[E6]

What is unknown

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

Last update in these facts: 2024-07-25 13:32 UTC · summary s1, evidence e26ce0adfe7712ff

Evidence (7)
  1. E1Loggly reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Account usage data missing". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2024-07-24 16:56 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Account Usage. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2024-07-25 13:32 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Account Usage

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Loggly 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 24, 2024, 16:56 UTCVendor-reported startVendor time
  2. Jul 25, 2024, 13:32 UTCVendor-reported resolutionVendor time

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