Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
A crawler hitting a 380k-page sitemap drove 800 billion D1 row reads and an $800.03 charge.
Community user faithalarmapp says Google crawling a 380,000-page sitemap generated 800 billion D1 row reads in one week (June 22 to 28, 2026), an unexpected $800.03 charge, and asks for a goodwill credit. A Cloudflare Customer Reliability Engineer replied that the payment redirect on the dashboard can be clicked through to open a billing ticket. After fixing caching and redirects, the author reports about four weeks later that the support case has no resolution and that the account was downgraded to the free tier.
What happened
- Reported cause
- Read volume
- Incident date
- 2026-06-22
- First reported
- 2026-06-29
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Personnel reply linked
Latest reported outcome
About four weeks after the request, the author reports no resolution and says the account was downgraded to the free tier.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports the read spike
Open original sourceThe author reports about 800 billion D1 row reads in one week from a sitemap crawl, adding $800.03, and asks for a goodwill credit.
Cloudflare engineer explains the dashboard redirect
Open original sourceA Cloudflare Customer Reliability Engineer says the author can click through the payment redirect by selecting "I Understand" and then open a ticket marked as a billing issue.
No resolution after four weeks
Open original sourceThe author says there has been no resolution and that the account was downgraded to the free tier.
More to read
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.
hung: Workers AI neuron charges billed despite expected free usage.
In a Hacker News comment, hung says that with paid Workers he was billed for confusing Workers AI neuron usage that should have been covered under usage limits, never got an answer on why, and that support ignored his ticket.
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.