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

Investigating CDN Configuration Synchronization

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

Official source (opens in a new tab)
Vendor start
Dec 14, 2025, 10:00 UTC
Vendor's clock
Resolved
Dec 16, 2025, 15:07 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 02:11 UTC
Statuswall's clock
Duration
2 d 5 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

  • CacheFly reports operational: "Investigating CDN Configuration Synchronization".[E1, E2]
  • The vendor marked it resolved at 2025-12-16 15:07 UTC.[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • 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: 2026-11-11 02:11 UTC · summary s1, evidence ff399ee5de6ac8cd

Evidence (8)
  1. E1CacheFly reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Investigating CDN Configuration Synchronization". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-12-14 10:00 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2025-12-16 15:07 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: not stated by the vendor

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. Dec 14, 2025, 10:00 UTCVendor-reported startVendor time
  2. Dec 16, 2025, 15:07 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:11 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall