Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
Patched app bug drove an R2 ListObjects spike and an about $18 charge.
sumedha.edu0 reports a webapp bug caused a massive R2 ListObjects (Class B) spike over May 14–15 (about 4.6M operations versus a normal baseline of about 10–130/day). The bug is patched. The author requests a billing credit for the about $18 charge and says support-case access failed with ErrorCode 41.
What happened
- Reported cause
- Read volume
- Incident date
- 2026-05-14
- First reported
- 2026-05-26
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author requests a billing credit after patching the bug; no staff outcome is in the thread.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author requests credit for R2 ListObjects spike
Open original sourceThe author reports about 4.6M Class B operations over two days from a patched bug and asks for credit on an about $18 charge.
More to read
Steven Menke: an Agents SDK bug and a reported $1,700 Durable Objects invoice.
Steven Menke (@Galorious_) reports that runaway Durable Objects caused by an Agents SDK bug produced a $1,700 invoice in three days, citing one trillion SQLite reads (a later post says writes). He says his support ticket, even after a maintainer escalated it, received no reply for months.
Check getAlarm() first and keep preview off real Durable Objects
@graycoin retells the Durable Object alarm loop shared by @shmily7 and draws three habits: check getAlarm() before setAlarm(), do not bind preview environments to real Durable Objects, and reread AI-generated storage and scheduling code.
Why hard spending caps take time: Ashley Peacock on billing latency
Ashley Peacock (@ashleypeacock), who works on Durable Objects at Cloudflare, explains from experience why near-real-time spending caps are hard to build, says hard billing caps are coming soon, and suggests budget alerts plus issue alerts in the meantime.