Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
nikhil_no_1: a $5 Containers-style subscription produced a $95 invoice.
Community user nikhil_no_1 says deploying a VPC to run openclaw on Cloudflare Workers was supposed to be a $5/month subscription, but the invoice charged $95. Ticket 01996691 had no response for about a month. A Cloudflare staff reply suspects charges for exceeding plan limits and points to the invoice breakdown.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2026-03-29
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Personnel reply linked
Latest reported outcome
Staff suggests the $95 may be overage beyond the $5 plan; the author still expects a refund and reports no ticket resolution after a month.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports $95 charge on a $5 subscription
Open original sourceThe author reports a $95 card charge after expecting a $5/month subscription for an openclaw VPC deployment, with ticket 01996691 unanswered for a month.
Staff points to overage beyond plan limits
Open original sourceA Cloudflare staff account says the charge may be for exceeding plan limits and to check the invoice breakdown.
More to read
Yan Zhu (picturepan2): about $400 from a D1 row-reads spike.
Yan Zhu (@picturepan2) says he also hit an about $400 Cloudflare bill the previous month when D1 database row reads spiked. He quotes the shmily7 Durable Objects thread for context and does not report a refund or support outcome.
Cloudflare Recognizer
An open-source Workers + KV tool that polls Cloudflare analytics on a cron, tracks usage against a contract commit on a custom billing cycle, and alerts on surges, aimed at Enterprise accounts.
A budget alert is a horn, not a brake
@GUYUE_LGY points to Cloudflare’s Budget alerts documentation: alerts send email when spend crosses a threshold but do not pause or cap usage. Before letting AI run unattended, the author checks what actually happens at the line.