Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
azrd: a renewal charged during a Registrar outage without renewing the domain.
Community user azrd says azrd.dev was renewed on July 7, 2026 and charged, but the domain did not renew, and links a Cloudflare Status notice about Registrar operations issues that day.
What happened
- Reported cause
- Unknown
- Incident date
- 2026-07-07
- First reported
- 2026-07-14
- Billing outcome
- Not recorded
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author offers to provide the receipt; the post was merged into another dispute topic and no outcome is reported.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports the disputed charge
Open original sourceThe author attributes the failure to the “Cloudflare Registrar operations issues” status incident. The amount is not stated.
More to read
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.
hfcorriez: $100+ of AI-driven extra usage over two months, reported cancelled after emails.
@hfcorriez says AI caused over $100 of extra consumption over two months. He says that after two rounds of email explaining the situation to Cloudflare, the charges were cancelled, and posts a screenshot of two negative line items (-$31.92 and -$75.42) marked Fully Applied.
A software defect drove a Durable Objects usage spike and a $3,800+ invoice; support declined a refund under standard policy.
Cloudflare Community user dev.in1 says a one-time software defect in their application sharply increased Durable Objects usage, mainly Storage Rows Written and Requests, producing an invoice of more than $3,800 for the September 2026 billing period. The author says the issue was identified, fixed and redeployed, with monitoring and alerts added. They report that support confirmed the usage was metered but said usage-based charges are not refundable under the standard policy, and they ask for escalation for a one-time courtesy adjustment.