Durable Objects alarm loop: about $112.35 a month on Workers Paid

A month that looks like the numbers below comes to roughly $112.35, base fee included. The meter that runs out first is Durable Objects requests (incl. alarms), at 5000% of its included usage. Prices are the public list as of 2026-09-15; the real invoice is the only truth.

Adjust the numbers → ← Usage Guard

Estimated bill

Total per month $112.35

Workers Paid base fee $5.00

Meter closest to (or past) its included usage: Durable Objects requests (incl. alarms) — 50M / 1M (5000%)

Overages

  • Durable Objects duration (GB-s): 7.6M → $100.00
  • Durable Objects requests (incl. alarms): 49M → $7.35

Usage assumed for the month

What this setup looks like

A Durable Object sets an alarm, does a little work when it fires, and sets the next alarm before returning. That is the documented pattern for periodic tasks. It goes wrong when the interval drifts down to a second, or the handler throws and the runtime retries, because every alarm invocation is a billable request and the object never sleeps.

Why Durable Objects requests (incl. alarms) runs out first

Workers Paid includes 1M Durable Objects requests a month. At 50M the object is at 5000% of that, yet the request overage is the small line here. An object that stays awake all month accrues about 2.6 million seconds of duration, billed in GB-seconds, and that is where most of the total comes from. Keeping an object alive costs more than calling it.

What to watch in GraphQL Analytics

Group durableObjectsInvocationsAdaptiveGroups by script and hour. A flat line near 3,600 requests an hour with no user traffic behind it is an alarm firing every second. Check wallTime next to it. The handler should call deleteAlarm() on a stop signal, and back off instead of rescheduling on error.

Prices and included usage copied from Cloudflare's public pricing pages on 2026-09-15. Approximate: some meters round up to the next unit, Workers AI and bandwidth are not included, and the real invoice is the only truth.

Background: the eight public Cloudflare bill incidents of 2026, seven of them D1 rows read

Other typical bills

Also exploring

Paying for Workers and wary of a surprise invoice? See Usage Guard — per-metric spike alerts and an optional stop switch.

Routing support@ through Cloudflare and reading it in Gmail? See Routed Inbox — a small shared inbox on Email Routing, no seat pricing.

Managing Cloudflare for many clients? See Zone Audit — config drift and baseline checks across accounts.