Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
Amras: charged for a year of services with no active domains.
Amras (@Amras80113423) tells Cloudflare he was charged for a year of services without any active domains and that billing support blew him off.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2025-06-11 11:34 UTC
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author says he contacted billing support and was blown off; no further 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 charge
Read on 𝕏The author writes that Cloudflare charged him for a year of services when he has no active domains and that billing support blew him off.
Amras
@Amras80113423 · Original 𝕏 post
@Cloudflare you charged me for a year of services when I don't have any active dimans and your billing support blew me off.. what's going with you guys...
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.
Cloudflare billing risk audit skill for coding agents
Kid (@singkid9527), who collects cases and guides for Billflare, open-sourced a skill that has a coding agent review a project's configuration and source in read-only mode for paths that can amplify Cloudflare costs.
An L7 DDoS pushed about 182 TB through Argo, an $18,232.50 charge.
Community user TravelTech says an April 2026 L7 DDoS attack peaking around 400k requests per second was routed through Argo Smart Routing before mitigation, generating about 182 TB of Argo usage and a disputed $18,232.50 charge. They say a billing case with attack logs was opened on April 29 and that their account executive confirmed in writing that the traffic was an attack and said finance would review, with no resolution after six weeks.