Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
b5844782: Workers Paid $5 plan produced a $61.18 charge without noticed usage.
Community user b5844782 says they activated Cloudflare Workers Paid in December for $5 but were charged $61.18 without actively using the service or receiving reminder notifications, and asks to cancel the unexpected charge.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2025-01-16
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
Staff points the author to Billing support paths; no refund outcome is reported in the thread.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports $61.18 charge on Workers Paid
Open original sourceThe author reports a $61.18 charge after activating a $5 Workers Paid plan, saying they did not actively use the service.
More to read
Put the spending ceiling into AI-generated code
Prasenjit Sarkar (@stretchcloud) uses the Durable Objects alarm loop to argue that alarms bill without traffic, that a single console cap cannot cover multi-vendor agent work, and that generated code needs execution quotas, idempotency checks and a kill switch.
lojabelastock: $22.50 for about 4.07 million R2 Class A ops during development.
Community user lojabelastock reports invoice IN-83391537 for $22.50 covering 4,070,034 R2 Storage Class A Operations during automated development/testing of Bela Stock, asks to cancel the invoice or issue a one-time courtesy credit, and says an autorun routine was removed afterward.
Cloudflare billing pitfalls thread
The author organizes Cloudflare billing risks by product and shares experience with budget alert emails.