Cloudflare changes Durable Object placement to reduce repeat cold starts
Cloudflare changed how inactive Durable Objects restart, according to its November 9 changelog. When possible, a reactivated object returns to the machine that previously ran it, avoiding another load of its data. Announcement
The company says the change is live in every region and requires no customer action. It may reduce cold starts for SQLite-backed objects that resume shortly after becoming idle, but benefits depend on traffic and workload. Cloudflare provides no quantified latency improvement in the announcement.
For developers using Durable Objects to hold application or agent state, the practical question is whether their own stop-and-resume pattern benefits. That is an operational implication, not a measured result from this reporting. The change offers a narrower performance improvement than a guarantee of warm starts.
Sources
- Cloudflare changes Durable Object placement to reduce repeat cold starts (primary; 2026-11-09)
Sources and citations
Revision history
Published .