Cloudflare Status · History · Incident #5242
RESOLVEDWorkers Builds Increased Failure Rate
Minor · Started Jul 8, 2026 · 6:37 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Cloudflare Status · History · Incident #5242
RESOLVEDMinor · Started Jul 8, 2026 · 6:37 PM
Duration
< 1m
Severity
Minor
Detection lead
—
User reports
Peak 1/hr
Summary
Cloudflare has identified and mitigated an issue which impacted a small subset of projects running Workers Builds between 2026-07-07 20:10 UTC to 2026-07-08 18:30 UTC. Customers experiencing the issue will have seen their builds fail with the error "A Worker named <worker-name> already exists in your account...".
Started
Jul 8, 2026 · 6:37 PM
Resolved
Jul 8, 2026 · 6:37 PM
Duration
< 1m
Severity
None
Event timeline
Resolved
Jul 8 · 6:37 PM CloudflareCloudflare has identified and mitigated an issue which impacted a small subset of projects running Workers Builds between 2026-07-07 20:10 UTC to 2026-07-08 18:30 UTC. Customers experiencing the issue will have seen their builds fail with the error "A Worker named <worker-name> already exists in your account...".
User reports · incident window
Hourly report count. Red bars mark the incident window.
Peak: 1 reports/hr
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026