Oct 29, 11:49 UTC Resolved - This incident has been resolved. Oct 29, 11:37 UTC Monitoring - We are continuing to monitor for any further issues. Oct 29, 10:51 UTC Identified - The issue has been identified and a fix is being implemented.
Durable Objects can stay active across requests, allowing you to run long-running agents, maintain long-lived WebSocket connections and coordinate state across many clients. This is possible because each Durable Object is globally unique, and this means it must run only one version of your code at a time. Previously, when you deployed a change to your Durable Objects code, that change would be applied immediately, which could interrupt in-flight work and terminate open connections. Durable Objects now defer code updates by default. When you deploy, an active Durable Object can keep running its current code for up to 5 minutes (300 seconds) while it waits to hibernate. This gives in-flight work time to finish. WebSocket connections that use the Hibernation API remain connected when an object adopts new code after hibernating.
Source Cloudflare DevelopersCC BY 4.0 · Publisher excerpt shortened and converted to plain text. Original source license applies.
Cloudflare now preserves Workers context when a subrequest targets a Cloudflare-proxied hostname using Bring Your Own IP (BYOIP). These requests are identified as Cloudflare-to-Cloudflare traffic instead of external Internet traffic. Previously, some BYOIP subrequests could lose Workers context and original client signals. This could cause security rules to behave unexpectedly, Bot Management to evaluate an internal Cloudflare connection instead of the original client, or affected requests to return false 403 responses. Workers subrequests to BYOIP destinations now preserve the CF-Worker header and cf.worker.upstream_zone field. This supports consistent security rule evaluation across same-zone and cross-zone subrequests. Bot Management fields on the destination zone now represent the original end-user connection for affected BYOIP subrequests.
Source Cloudflare DevelopersCC BY 4.0 · Publisher excerpt shortened and converted to plain text. Original source license applies.
Oct 29, 11:47 UTC Resolved - This incident has been resolved. Oct 29, 10:06 UTC Identified - Cloudflare is investigating issues causing degraded availability and elevated error rates for Durable Objects in Eastern Europe (EEUR2 region).
Workers Static Assets can now serve assets from a URL path prefix without changing their directory structure. Set assets.base_path in Wrangler, or worker.assets.basePath in cloudflare.config.ts. Use Wrangler 4.148.0 ↗︎ or later. With cloudflare.config.ts, use cf 1.0.0-beta.13 ↗︎ or later. For example, this configuration serves your built assets from /blog/: Select your preferred CLI WranglerCF Changes examples on this page to use the selected CLI.
Source Cloudflare DevelopersCC BY 4.0 · Publisher excerpt shortened and converted to plain text. Original source license applies.
Workers Builds now retains each build and its build logs for 90 days after the build finishes. You can find them under View build history in your Worker's Deployments tab, or through the Workers Builds API. After 90 days, a build and its logs are removed. The versions and deployments it created stay in your Worker's version history, so you can still roll back to them. If you need a build's logs for longer, you can download them with the Get build logs API endpoint. For more information, refer to the Workers Builds limits documentation.
Source Cloudflare DevelopersCC BY 4.0 · Publisher excerpt shortened and converted to plain text. Original source license applies.
Oct 27, 22:58 UTC Resolved - This incident has been resolved. Oct 27, 22:48 UTC Monitoring - We are continuing to monitor for any further issues. Oct 27, 22:30 UTC Identified - We are continuing to work on a fix for the issue.