Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
bimbimbu: Log Explorer left on during a DDoS produced a $25,000 September charge.
Community user bimbimbu reports an unexpected $25,000 charge in September 2025 versus usual monthly bills under $200, after Log Explorer was accidentally left enabled during a DDoS that spiked traffic and logs. The author disabled Log Explorer, says safeguards are being added, and notes a support ticket unanswered for two days at posting time.
What happened
- Reported cause
- Traffic spike
- Incident date
- 2025-09-01
- First reported
- 2025-10-04
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author reports an open support ticket with no response for two days at the time of the post; no billing outcome is stated.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports $25k Log Explorer + DDoS charge
Open original sourceThe author attributes a $25,000 September charge to Log Explorer left enabled during a DDoS, versus usual bills under $200.
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.
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.
Free plan FAQ: overage errors, reset time and CPU limits
风易 (@Michael_liyang) answers three common questions: whether going over the free quota silently charges you, when quotas reset, and whether the free plan can be used commercially.