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

LAX DNS Availability

Reported by CacheFly · Hosting, CDN & Edge · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Jan 26, 2026, 09:15 UTC
Vendor's clock
Resolved
Jan 26, 2026, 22:04 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 02:11 UTC
Statuswall's clock
Duration
12 h 49 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

  • CacheFly reports degraded: "LAX DNS Availability".[E1, E2]
  • The vendor marked it resolved at 2026-01-26 22:04 UTC.[E3, E7]

Affected products and regions

  • Components: LAX1.[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: 2026-11-11 02:11 UTC · summary s1, evidence d2a5222dda804267

Evidence (8)
  1. E1CacheFly reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "LAX DNS Availability". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-01-26 09:15 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: LAX1. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-01-26 22:04 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 02:11 UTC. (Statuswall)

Affected scope

Not stated by the vendor

Components: LAX1

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

CacheFly 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. Jan 26, 2026, 09:15 UTCVendor-reported startVendor time
  2. Jan 26, 2026, 22:04 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:11 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall