ClaudeCloudflare Developer Platform2026/06/19 0:00

Durable Objects - Outbound connections keep Durable Objects alive

要点だけを先に読めるように短く再構成したセクションです。

元記事

Quick Digest

要約

要点だけを先に読めるように短く再構成したセクションです。

claudeja

Durable Objects - Outbound connections keep Durable Objects alive の要約

Key Points

  • ポイント1: Changelog New updates and improvements at Cloudflare.
  • ポイント2: Subscribe to RSS View RSS feeds ← Back to all posts Outbound connections keep Durable Objects alive Jun 19, 2026 Durable Objects Durable Objects now remain alive for the duration o
  • ポイント3: Previously, a Durable Object would be evicted after 70-140 seconds of no incoming traffic, even if the object had an open outbound connection, which is a common pattern when stream

Summary

この記事は 2026-06-19 に公開された「Durable Objects - Outbound connections keep Durable Objects alive」の内容を日本語で簡潔にまとめたものです。

Key Points

  • ポイント1: Changelog New updates and improvements at Cloudflare.
  • ポイント2: Subscribe to RSS View RSS feeds ← Back to all posts Outbound connections keep Durable Objects alive Jun 19, 2026 Durable Objects Durable Objects now remain alive for the duration o
  • ポイント3: Previously, a Durable Object would be evicted after 70-140 seconds of no incoming traffic, even if the object had an open outbound connection, which is a common pattern when stream

Full Translation

翻訳

原文の流れを保ったまま読める翻訳セクションです。

claudeja

Durable Objects - Outbound connections keep Durable Objects alive(原文タイトル)

概要

公開日: 2026-06-19 翻訳生成に失敗したため、原文をそのまま保存しています。

原文

Changelog New updates and improvements at Cloudflare. Subscribe to RSS View RSS feeds ← Back to all posts Outbound connections keep Durable Objects alive Jun 19, 2026 Durable Objects Durable Objects now remain alive for the duration of active outbound connections created via connect() or an outbound WebSocket. Previously, a Durable Object would be evicted after 70-140 seconds of no incoming traffic, even if the object had an open outbound connection, which is a common pattern when streaming responses from a large language model (LLM) over TCP or an outbound WebSocket. With this change, each active outbound connection prevents eviction. Once all outbound connections close, the standard 70-140 second inactivity window applies before the Durable Object is evicted. Before: streaming connections were cut off by eviction After: active outbound connections keep the Durable Object alive If you are building agents on Cloudflare , this is especially relevant. An agent that streams tokens from an LLM while calling models , or that performs long-running tasks over an outbound connection, now stays alive for the duration of that connection instead of being evicted mid-stream. Limits: Each outbound connection keeps the Durable Object alive for a maximum of 15 minutes . After 15 minutes, the connection stops preventing eviction (the connection itself continues operating), and the standard eviction rules resume. The Durable Object's existing per-account instance limits still apply. For more information, refer to Lifecycle of a Durable Object . Resources API New to Cloudflare? Directory Sponsorships Open Source Cloudflare Research Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Cloudflare Labs Speed Test Is BGP Safe Yet? Certificate Transparency Community Community forum X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings Was this helpful? Yes No