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

CDN Acceleration 502s on DNS Records

Reported by Bunny.net · Hosting, CDN & Edge · source last read 13 min ago

Official source (opens in a new tab)
Vendor start
May 22, 2026, 11:19 UTC
Vendor's clock
Resolved
May 23, 2026, 13:52 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 d 2 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

  • Bunny.net reports degraded: "CDN Acceleration 502s on DNS Records".[E1, E2]
  • The vendor marked it resolved at 2026-05-23 13:52 UTC.[E3, E7]

Affected products and regions

  • Components: CDN, DNS.[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-05-23 13:52 UTC · summary s1, evidence e17cad0c44b3ee0c

Evidence (7)
  1. E1Bunny.net reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "CDN Acceleration 502s on DNS Records". (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-22 11:19 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: CDN, DNS. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-05-23 13:52 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: CDN, DNS

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

Bunny.net 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 22, 2026, 11:19 UTCVendor-reported startVendor time
  2. May 23, 2026, 13:52 UTCVendor-reported resolutionVendor time

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