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

Increased Errors for Browser Run

Reported by Cloudflare · Hosting, CDN & Edge · source last read just now

Official source (opens in a new tab)
Vendor start
Oct 30, 2026, 02:41 UTC
Vendor's clock
Resolved
Oct 30, 2026, 03:48 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 h 7 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

  • Cloudflare reports degraded: "Increased Errors for Browser Run".[E1, E2]
  • The vendor marked it resolved at 2026-10-30 03:48 UTC.[E3, E7]

Affected products and regions

  • Components: Browser Run.[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-10-30 03:48 UTC · summary s1, evidence 42f08609c18032bb

Evidence (7)
  1. E1Cloudflare reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Increased Errors for Browser Run". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-10-30 02:41 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Browser Run. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-10-30 03:48 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Browser Run

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

Cloudflare 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. Oct 30, 2026, 02:41 UTCVendor-reported startVendor time
  2. Oct 30, 2026, 03:48 UTCVendor-reported resolutionVendor time

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