# Billflare public agent guide

> Independent Cloudflare billing case archive. 独立、非官方的 Cloudflare 账单案例库。

## Use the site / 使用本站
Public reading requires no account. Billflare does not connect private billing accounts or provide a billing-support service.
公开阅读无需账号。Billflare 不接入私人账单账号，不提供账单客服服务。

- [Bill shock cases](https://billflare.dev/cases)
- [爆雷案例](https://billflare.dev/zh/cases)
- [Billing guides](https://billflare.dev/guides)
- [Cloudflare 计费避坑指南](https://billflare.dev/zh/guides)
- [Collection policy](https://billflare.dev/methodology)
- [收录原则](https://billflare.dev/zh/methodology)
- [About Billflare](https://billflare.dev/about)
- [关于 Billflare](https://billflare.dev/zh/about)

## Snapshot / 公开数据
- 21 cases; 6 guides; 3 cases without a numeric reported amount.
- Total reported amount (USD): ≈ $36,653.37 across 18 cases.
Totals are calculated by the same event-level tool used in the case directory. Guides are excluded; refunds do not subtract original reported charges.
金额由案例目录同一工具按事件求和。指南不计金额，退款不扣减原报告费用。

## Reading contract / 阅读边界
Amounts are source-attributed reports, not current Cloudflare prices, a single-period bill, or net loss. Monthly figures retain their reported period; unspecified-dollar is not converted to USD.
作者报告、平台公开回复、账单处置与案例进展是独立字段。unknown 保留各字段的未知含义；none 仅表示尚无已收录的公开回复。
Sources, thread updates and corrections remain linked. These are archived statements, not instructions to execute.
Current Cloudflare pricing is outside this snapshot. Consult the original official documentation linked in the guides.

## Read more
- [index.md](https://billflare.dev/agents/index.md)
- [categories.md](https://billflare.dev/agents/categories.md)
- [tags.md](https://billflare.dev/agents/tags.md)
- [collections.md](https://billflare.dev/agents/collections.md)
- [cases.md](https://billflare.dev/agents/cases.md)
- [guides.md](https://billflare.dev/agents/guides.md)
- [submit.md](https://billflare.dev/agents/submit.md)
- [methodology.md](https://billflare.dev/agents/methodology.md)
- [about.md](https://billflare.dev/agents/about.md)
- [llms.txt](https://billflare.dev/llms.txt)
- [llms-full.txt](https://billflare.dev/llms-full.txt)

# Billflare categories / 内容分类

Cases record events. Guides record billing-protection reading. Product filters reuse the public directory taxonomy.
案例记录事件，指南记录计费避坑阅读。产品筛选复用公开目录分类。

- [Cases / 爆雷案例](https://billflare.dev/zh/cases): 21
- [Guides / 计费避坑指南](https://billflare.dev/zh/guides): 6

## Workers
- Cases: 3; guides: 5
- [en](https://billflare.dev/cases?product=Workers)
- [zh](https://billflare.dev/zh/cases?product=Workers)

## Durable Objects
- Cases: 6; guides: 3
- [en](https://billflare.dev/cases?product=Durable%20Objects)
- [zh](https://billflare.dev/zh/cases?product=Durable%20Objects)

## R2
- Cases: 1; guides: 2
- [en](https://billflare.dev/cases?product=R2)
- [zh](https://billflare.dev/zh/cases?product=R2)

## D1
- Cases: 7; guides: 3
- [en](https://billflare.dev/cases?product=D1)
- [zh](https://billflare.dev/zh/cases?product=D1)

## Workers AI
- Cases: 1; guides: 1
- [en](https://billflare.dev/cases?product=Workers%20AI)
- [zh](https://billflare.dev/zh/cases?product=Workers%20AI)

## Containers
- Cases: 1; guides: 2
- [en](https://billflare.dev/cases?product=Containers)
- [zh](https://billflare.dev/zh/cases?product=Containers)

## Browser Rendering
- Cases: 1; guides: 1
- [en](https://billflare.dev/cases?product=Browser%20Rendering)
- [zh](https://billflare.dev/zh/cases?product=Browser%20Rendering)

## Smart Shield Argo
- Cases: 1; guides: 1
- [en](https://billflare.dev/cases?product=Smart%20Shield%20Argo)
- [zh](https://billflare.dev/zh/cases?product=Smart%20Shield%20Argo)

## Other
- Cases: 0; guides: 1
- [en](https://billflare.dev/cases?product=Other)
- [zh](https://billflare.dev/zh/cases?product=Other)


## Read more
- [index.md](https://billflare.dev/agents/index.md)
- [categories.md](https://billflare.dev/agents/categories.md)
- [tags.md](https://billflare.dev/agents/tags.md)
- [collections.md](https://billflare.dev/agents/collections.md)
- [cases.md](https://billflare.dev/agents/cases.md)
- [guides.md](https://billflare.dev/agents/guides.md)
- [submit.md](https://billflare.dev/agents/submit.md)
- [methodology.md](https://billflare.dev/agents/methodology.md)
- [about.md](https://billflare.dev/agents/about.md)
- [llms.txt](https://billflare.dev/llms.txt)
- [llms-full.txt](https://billflare.dev/llms-full.txt)

# Billflare reported-cause tags / 报告原因标签

These labels organize explanations given in sources. They are not Billflare technical diagnoses or confidence ratings.
标签整理来源给出的原因说明，不是本站技术诊断或可信度等级。指南不强加事故原因标签。

## Repeated polling / 重复轮询
- ID: polling; cases: 2
- [en](https://billflare.dev/cases?cause=polling)
- [zh](https://billflare.dev/zh/cases?cause=polling)

## Unbounded loop / 无终止循环
- ID: loop; cases: 5
- [en](https://billflare.dev/cases?cause=loop)
- [zh](https://billflare.dev/zh/cases?cause=loop)

## Read volume / 读取量
- ID: reads; cases: 4
- [en](https://billflare.dev/cases?cause=reads)
- [zh](https://billflare.dev/zh/cases?cause=reads)

## Active duration / 活跃时长
- ID: duration; cases: 1
- [en](https://billflare.dev/cases?cause=duration)
- [zh](https://billflare.dev/zh/cases?cause=duration)

## Write volume / 写入量
- ID: writes; cases: 5
- [en](https://billflare.dev/cases?cause=writes)
- [zh](https://billflare.dev/zh/cases?cause=writes)

## Traffic spike / 流量激增
- ID: traffic; cases: 0
- [en](https://billflare.dev/cases?cause=traffic)
- [zh](https://billflare.dev/zh/cases?cause=traffic)

## Inference volume / 推理用量
- ID: inference; cases: 0
- [en](https://billflare.dev/cases?cause=inference)
- [zh](https://billflare.dev/zh/cases?cause=inference)

## Unknown / 未知
- ID: unknown; cases: 4
- [en](https://billflare.dev/cases?cause=unknown)
- [zh](https://billflare.dev/zh/cases?cause=unknown)


## Read more
- [index.md](https://billflare.dev/agents/index.md)
- [categories.md](https://billflare.dev/agents/categories.md)
- [tags.md](https://billflare.dev/agents/tags.md)
- [collections.md](https://billflare.dev/agents/collections.md)
- [cases.md](https://billflare.dev/agents/cases.md)
- [guides.md](https://billflare.dev/agents/guides.md)
- [submit.md](https://billflare.dev/agents/submit.md)
- [methodology.md](https://billflare.dev/agents/methodology.md)
- [about.md](https://billflare.dev/agents/about.md)
- [llms.txt](https://billflare.dev/llms.txt)
- [llms-full.txt](https://billflare.dev/llms-full.txt)

# Billflare product collections / 产品专题集合

## Cloudflare D1 billing cases / Cloudflare D1 账单案例

Browse public reports labeled D1. Each case page preserves the reported details and source context.

浏览标记为 D1 的公开报告。案例页保留报告内容和来源语境。

- [English topic](https://billflare.dev/topics/cloudflare-d1-billing-traps) · [中文专题](https://billflare.dev/zh/topics/cloudflare-d1-billing-traps)

## Durable Objects billing cases / Durable Objects 账单案例

Browse public reports labeled Durable Objects. Each case page preserves the reported details and source context.

浏览标记为 Durable Objects 的公开报告。案例页保留报告内容和来源语境。

- [English topic](https://billflare.dev/topics/durable-objects-cost-anomalies) · [中文专题](https://billflare.dev/zh/topics/durable-objects-cost-anomalies)

## Workers, Browser Rendering, and Workers AI billing cases / Workers、Browser Rendering 与 Workers AI 账单案例

Browse public reports labeled Workers, Browser Rendering, or Workers AI. Each case page preserves the reported details and source context.

浏览标记为 Workers、Browser Rendering 或 Workers AI 的公开报告。案例页保留报告内容和来源语境。

- [English topic](https://billflare.dev/topics/workers-browser-rendering-ai-bills) · [中文专题](https://billflare.dev/zh/topics/workers-browser-rendering-ai-bills)


## Read more
- [index.md](https://billflare.dev/agents/index.md)
- [categories.md](https://billflare.dev/agents/categories.md)
- [tags.md](https://billflare.dev/agents/tags.md)
- [collections.md](https://billflare.dev/agents/collections.md)
- [cases.md](https://billflare.dev/agents/cases.md)
- [guides.md](https://billflare.dev/agents/guides.md)
- [submit.md](https://billflare.dev/agents/submit.md)
- [methodology.md](https://billflare.dev/agents/methodology.md)
- [about.md](https://billflare.dev/agents/about.md)
- [llms.txt](https://billflare.dev/llms.txt)
- [llms-full.txt](https://billflare.dev/llms-full.txt)

# Billflare billing cases / 账单案例

## moltworker: a reported $81 monthly bill, not the expected $5. / moltworker：预期每月 $5，报告账单却是 $81。

- ID: ahmetb-moltworker-containers
- Product: Containers
- [English page](https://billflare.dev/cases/ahmetb-moltworker-containers) · [中文页面](https://billflare.dev/zh/cases/ahmetb-moltworker-containers)
- Reported amount: $81
- Currency: USD; period: monthly; qualifier: exact
- Reported cause: duration
- Billing action: unknown; attribution: unknown
- Case progress: unknown; attribution: unknown
- Public reply archive status: staff
- Reported at: 2026-03-03
- [Original report](https://x.com/ahmetb/status/2028697956115984538)

Ahmet Alp Balkan (@ahmetb) reports an $81 monthly bill after running moltworker, compared with a $5/month expectation from the repository. Mike Nomitch identifies himself as the Containers PM and invites Ahmet to DM with details.

Ahmet Alp Balkan（@ahmetb）称运行 moltworker 后月账单为 $81，与仓库给出的每月 $5 预期不符。Mike Nomitch 自称 Containers PM，并邀请 Ahmet 私信提供详情。

In his reply, Mike Nomitch identifies himself as the Containers PM and invites Ahmet to DM with details.

Mike Nomitch 在回复中自称 Containers PM，并邀请 Ahmet 私信提供详情。

### Timeline / 后续
- 2026-03-03: Monthly bill exceeds the expectation / 月账单高于预期
  The author reports an $81 monthly bill after running the project for a month, compared with a $5/month expectation. / 作者称运行项目一个月后，月账单为 $81，而预期为每月 $5。
  [Source / 原帖](https://x.com/ahmetb/status/2028697956115984538)
- 2026-03-03: Author describes pricing-document changes / 作者补充定价文档变化
  The author says a later commit added a container-time price estimate and reduced Worker size. / 作者称后续提交加入容器时长估价，并缩小了 Worker 规格。
  [Source / 原帖](https://x.com/ahmetb/status/2028698446526644540)
- 2026-03-03: Self-identified Containers PM offers help / 自称 Containers PM 的人员提出协助
  Mike Nomitch identifies himself as the Containers PM and asks Ahmet to DM with details. / Mike Nomitch 自称 Containers PM，并请 Ahmet 私信提供详情。
  [Source / 原帖](https://x.com/MikeNomitch/status/2028707969928704468)

### Sources / 来源
- [Original monthly-bill report / 原始月账单报告](https://x.com/ahmetb/status/2028697956115984538) (source)
- [Author’s pricing clarification / 作者的定价补充](https://x.com/ahmetb/status/2028698446526644540) (source)
- [Self-identified product-personnel reply / 自称产品人员的回复](https://x.com/MikeNomitch/status/2028707969928704468) (staff)

## D1: an author reports a $3,500 bill in 48 hours and a full waiver. / D1：作者报告 48 小时约 $3,500 账单，后称全额减免。

- ID: darylginn-d1-missing-index
- Product: D1
- [English page](https://billflare.dev/cases/darylginn-d1-missing-index) · [中文页面](https://billflare.dev/zh/cases/darylginn-d1-missing-index)
- Reported amount: ≈ $3,500
- Currency: USD; period: unknown; qualifier: approximate
- Reported cause: reads
- Billing action: waived; attribution: author-reported
- [Billing action source](https://x.com/darylginn/status/2082413530243043780)
- Case progress: resolved; attribution: author-reported
- Public reply archive status: none
- Reported at: 2026-07-29
- [Original report](https://x.com/darylginn/status/2082394623448961409)

@darylginn reports about $3,500 in D1 charges over 48 hours. He says an AI-assisted Postgres migration omitted indexes and caused about 970 billion row reads daily, and that Cloudflare waived the bill.

@darylginn 报告 D1 在 48 小时内产生约 $3,500 费用。他称 AI 辅助迁移 Postgres 时漏建索引，每日读取约 9700 亿行，并称 Cloudflare 豁免了账单。

The author says Cloudflare waived the full D1 bill as a goodwill gesture.

作者称 Cloudflare 出于善意豁免了整笔 D1 账单。

### Timeline / 后续
- 2026-07-29: Author reports a waived bill / 作者称账单获减免
  The author says Cloudflare waived an accidental $3.5k bill. / 作者称 Cloudflare 豁免了一笔意外产生的 $3.5k 账单。
  [Source / 原帖](https://x.com/darylginn/status/2082394623448961409)
- 2026-07-29: Amount and 48-hour context / 补充金额与 48 小时上下文
  The author reports $3.5k of D1 charges in 48 hours and a full goodwill waiver. / 作者报告 48 小时 D1 费用 $3.5k，并称获全额善意减免。
  [Source / 原帖](https://x.com/darylginn/status/2082413530243043780)
- 2026-07-29: Migration and row-read explanation / 补充迁移与行读取原因
  The author says an AI-assisted Postgres-to-D1 migration omitted indexes, producing about 970 billion reads a day. / 作者称 AI 辅助 Postgres 迁移至 D1 时漏建索引，每天产生约 9700 亿次读取。
  [Source / 原帖](https://x.com/darylginn/status/2082420017367564431)

### Sources / 来源
- [First located waiver report / 目前找到的首次减免陈述](https://x.com/darylginn/status/2082394623448961409) (source)
- [Amount and duration report / 金额与时长报告](https://x.com/darylginn/status/2082413530243043780) (source)
- [Author-reported missing indexes / 作者陈述漏建索引](https://x.com/darylginn/status/2082420017367564431) (source)

## Sitemap polling: the author reports a $100 Cloudflare bill alongside AWS costs. / sitemap 轮询：作者报告 CF 100 刀，与 AWS 费用分开记录。

- ID: enzyme-dev-workers-sitemap-polling
- Product: Workers
- [English page](https://billflare.dev/cases/enzyme-dev-workers-sitemap-polling) · [中文页面](https://billflare.dev/zh/cases/enzyme-dev-workers-sitemap-polling)
- Reported amount: $100
- Currency: USD; period: unknown; qualifier: exact
- Reported cause: polling
- Billing action: unknown; attribution: unknown
- Case progress: unknown; attribution: unknown
- Public reply archive status: none
- Reported at: 2026-10-04
- [Original report](https://x.com/enzyme_dev/status/2106741394371166701)

@enzyme_dev says a refactor made Workers fetch a sitemap every five seconds. In an October 6 reply, he reports a $100 Cloudflare bill and an AWS bill above $800 for the previous week.

@enzyme_dev 称重构后 Workers 每 5 秒拉取 sitemap。10 月 6 日的回复称上周 Cloudflare 账单为 $100，AWS 账单超过 $800。

The author reports $100 for Cloudflare and over $800 for AWS in a later reply. His earlier thread describes the August sitemap refactor.

作者在后续回复中报告 Cloudflare $100、AWS 超过 $800。较早的串文描述了 8 月的 sitemap 重构。

### Timeline / 后续
- 2026-10-04: Sitemap polling and quota exhaustion / 报告 sitemap 轮询与额度耗尽
  The author says Workers fetched a sitemap every five seconds after an August refactor, alongside higher AWS bandwidth costs. / 作者称 8 月重构后 Workers 每 5 秒拉取 sitemap，同时 AWS 带宽成本增加。
  [Source / 原帖](https://x.com/enzyme_dev/status/2106741394371166701)
- 2026-10-06: Later reply gives a CF amount / 后续回复给出 CF 金额
  On October 6, the author reports a $100 Cloudflare bill and an AWS bill above $800 for the previous week. / 10 月 6 日，作者报告上周 Cloudflare 账单为 $100，AWS 账单超过 $800。
  [Source / 原帖](https://x.com/enzyme_dev/status/2107543998139424987)

### Sources / 来源
- [Original polling account / 原始轮询陈述](https://x.com/enzyme_dev/status/2106741394371166701) (source)
- [CF amount in a later reply / 后续回复中的 CF 金额](https://x.com/enzyme_dev/status/2107543998139424987) (source)

## Workers and Queues: an author reports a jump from $5 to $2,145. / Workers 与 Queues：作者称账单从 $5 涨至 $2,145。

- ID: goteap-workers-queues-loop
- Product: Workers
- [English page](https://billflare.dev/cases/goteap-workers-queues-loop) · [中文页面](https://billflare.dev/zh/cases/goteap-workers-queues-loop)
- Reported amount: $2,145
- Currency: USD; period: unknown; qualifier: exact
- Reported cause: loop
- Billing action: refund-unavailable; attribution: author-reported
- [Billing action source](https://x.com/goteap/status/1992153210090602894)
- Case progress: unknown; attribution: author-reported
- Public reply archive status: none
- Reported at: 2025-11-22
- [Original report](https://x.com/goteap/status/1992153210090602894)

@goteap reports that a code loop generated over two billion internal requests and raised an invoice from $5 to $2,145. The author says a refund was not possible.

@goteap 报告代码循环产生超过 20 亿次内部请求，账单从 $5 涨至 $2,145。作者称无法退款。

The author says a refund was not possible.

作者称无法退款。

### Timeline / 后续
- 2025-11-22: Loop and unexpected bill reported / 报告循环与意外账单
  The author says a code bug caused a permanent loop with over two billion internal requests, raising the invoice from $5 to $2,145. He says a refund was not possible. / 作者称代码 bug 造成永久循环与超过 20 亿次内部请求，账单从 $5 涨至 $2,145。他称无法退款。
  [Source / 原帖](https://x.com/goteap/status/1992153210090602894)
- 2025-11-22: A colleague seeks a response / 同事尝试联系官方
  Alex tags CloudflareDev and CloudflareHelp in the thread. / Alex 在串中点名 CloudflareDev 与 CloudflareHelp。
  [Source / 原帖](https://x.com/alexpagepilot/status/1992164824252575987)

### Sources / 来源
- [Original report and refund claim / 原始报告与退款陈述](https://x.com/goteap/status/1992153210090602894) (source)
- [Colleague’s request for a response / 同事请求回复](https://x.com/alexpagepilot/status/1992164824252575987) (source)

## A 12 MB D1 database, a reported USD 1,966.35 invoice. / 12 MB 的 D1 数据库，作者报告 USD 1,966.35 发票。

- ID: imselmon-d1-write-volume
- Product: D1
- [English page](https://billflare.dev/cases/imselmon-d1-write-volume) · [中文页面](https://billflare.dev/zh/cases/imselmon-d1-write-volume)
- Reported amount: $1,966.35
- Currency: USD; period: unknown; qualifier: exact
- Reported cause: writes
- Billing action: unknown; attribution: unknown
- Case progress: unknown; attribution: unknown
- Public reply archive status: none
- Reported at: 2026-09-16
- [Original report](https://x.com/imselmon/status/2100200960232739325)

@imselmon reports a USD $1,966.35 D1 invoice for a roughly 12 MB database with over two billion row writes. The author says the activity is abnormal and is investigating the database usage.

@imselmon 报告约 12 MB 数据库产生 USD $1,966.35 D1 发票，并显示超过 20 亿行写入。作者称操作异常，正在排查数据库用量。

The author says he is investigating the unusually high D1 row writes and tags Cloudflare support accounts.

作者称正在排查异常偏高的 D1 行写入，并点名 Cloudflare 支持账号。

### Timeline / 后续
- 2026-09-16: D1 invoice and write volume reported / 报告 D1 发票与写入量
  The author reports USD $1,966.35, a roughly 12 MB database and over two billion row writes. / 作者报告 USD $1,966.35、约 12 MB 数据库与超过 20 亿行写入。
  [Source / 原帖](https://x.com/imselmon/status/2100200960232739325)
- 2026-09-16: Support requested publicly / 公开请求支持
  The author tags CloudflareDev, CloudflareHelp and Cloudflare. / 作者点名 CloudflareDev、CloudflareHelp 与 Cloudflare。
  [Source / 原帖](https://x.com/imselmon/status/2100201150247309443)

### Sources / 来源
- [Original USD invoice report / 原始 USD 发票报告](https://x.com/imselmon/status/2100200960232739325) (source)
- [Public support request / 公开支持请求](https://x.com/imselmon/status/2100201150247309443) (source)

## Jason Silberman: an approximately $1,000 AI-billing dispute, later reported resolved. / Jason Silberman：约千刀 AI 计费争议，后称已解决。

- ID: jason-silberman-ai-billing
- Product: Workers AI
- [English page](https://billflare.dev/cases/jason-silberman-ai-billing) · [中文页面](https://billflare.dev/zh/cases/jason-silberman-ai-billing)
- Reported amount: ≈ $1,000
- Currency: USD; period: unknown; qualifier: approximate
- Reported cause: unknown
- Billing action: unknown; attribution: unknown
- Case progress: resolved; attribution: author-reported
- Public reply archive status: staff
- Reported at: 2026-07-08
- [Original report](https://x.com/_jasonsilberman/status/2074671970860282100)

@_jasonsilberman reports an invoice around $1,000 with AI usage rows he says were duplicated and already prepaid. Cloudflare personnel reply, including Matthew Prince, who says the case was escalated. The author later says the issue was resolved.

@_jasonsilberman 报告约 $1,000 发票，称 AI 用量行项目重复且已预付。Cloudflare 人员回复，Matthew Prince 称已升级跟进。作者后称问题已解决。

The author says the issue was resolved later that day after Cloudflare personnel replied and Matthew Prince escalated the case.

Cloudflare 人员回复、Matthew Prince 升级跟进后，作者当日称问题已解决。

### Timeline / 后续
- 2026-07-08: Duplicate AI billing alleged / 指称 AI 用量重复计费
  The author reports an invoice around $1,000, duplicated AI usage rows, a mismatch with prepaid usage and a week waiting on an urgent ticket. / 作者报告约 $1,000 发票、重复 AI 用量行项目、与预付用量不符，并称紧急工单已等待一周。
  [Source / 原帖](https://x.com/_jasonsilberman/status/2074671970860282100)
- 2026-07-08: Personnel reply recorded / 记录人员回复
  Sunil Pai replies, “sorry about that.” / Sunil Pai 回复：“抱歉发生这种情况。”
  [Source / 原帖](https://x.com/threepointone/status/2074680377244086529)
- 2026-07-08: Escalation acknowledged / 回复称已升级跟进
  Matthew Prince says the case was escalated and apologizes for the trouble. / Matthew Prince 称案件已升级跟进，并为困扰致歉。
  [Source / 原帖](https://x.com/eastdakota/status/2074748012060938675)
- 2026-07-08: Additional personnel reply / 另一条人员回复
  Sid Chatterjee asks whether the author is sorted and says he is working with Dmitry Alexeenko to improve support. / Sid Chatterjee 询问问题是否已解决，并称正与 Dmitry Alexeenko 合作改进支持。
  [Source / 原帖](https://x.com/SidChatterjee/status/2074812623904784437)
- 2026-07-08: Author reports resolution / 作者称问题已解决
  The author says Cloudflare responded and helped resolve the issue. / 作者称 Cloudflare 作出回应并帮助解决了问题。
  [Source / 原帖](https://x.com/_jasonsilberman/status/2074853886616055831)

### Sources / 来源
- [Original AI-billing report / 原始 AI 计费报告](https://x.com/_jasonsilberman/status/2074671970860282100) (source)
- [Matthew Prince’s escalation reply / Matthew Prince 的升级回复](https://x.com/eastdakota/status/2074748012060938675) (staff)
- [Sunil Pai’s reply / Sunil Pai 的回复](https://x.com/threepointone/status/2074680377244086529) (staff)
- [Sid Chatterjee’s reply / Sid Chatterjee 的回复](https://x.com/SidChatterjee/status/2074812623904784437) (staff)
- [Author-reported resolution / 作者报告的解决](https://x.com/_jasonsilberman/status/2074853886616055831) (source)

## A voting page polling every three seconds: the author revises a $1,000 report. / 王小克：投票页每 3 秒轮询，千刀账单后补充用量明细。

- ID: keking99-workers-polling
- Product: Workers
- [English page](https://billflare.dev/cases/keking99-workers-polling) · [中文页面](https://billflare.dev/zh/cases/keking99-workers-polling)
- Reported amount: $816.52
- Currency: USD; period: unknown; qualifier: exact
- Reported cause: polling
- Billing action: unknown; attribution: unknown
- Case progress: unknown; attribution: unknown
- Public reply archive status: none
- Reported at: 2026-10-04
- [Original report](https://x.com/keking99/status/2106687001810677911)

@keking99 first reports about $1,000 for a voting page polling /api/result every three seconds. A later post reports $816.52 in accumulated usage as of October 4 and cites another screenshot total of $817.14.

@keking99 最初报告投票页每 3 秒轮询 /api/result 产生约 $1,000 费用。后称截至 10 月 4 日累计用量费为 $816.52，并另提截图合计 $817.14。

The author clarifies that polling drove usage and reports $816.52 in accumulated usage as of October 4.

作者澄清主要用量来自轮询，并报告截至 10 月 4 日累计用量费为 $816.52。

### Timeline / 后续
- 2026-10-04: Initial round-number report / 首次报告整数金额
  The author reports about $1,000 and 2.6 billion requests from a voting page polling every three seconds. / 作者报告约 $1,000 费用与 26 亿次请求，称投票页每 3 秒轮询。
  [Source / 原帖](https://x.com/keking99/status/2106687001810677911)
- 2026-10-04: Polling distinguished from caching / 区分轮询与缓存
  The author clarifies that polling, rather than caching itself, drove usage. / 作者澄清主要用量来自轮询，而不是缓存本身。
  [Source / 原帖](https://x.com/keking99/status/2106719404419641455)
- 2026-10-05: More precise usage breakdown / 补充更精确的用量明细
  The author reports $816.52 in accumulated usage for the September 11–October 10 billing period: $785.40 for requests and $31.12 for CPU. Another screenshot totals $817.14. / 作者报告 9 月 11 日至 10 月 10 日账期累计用量 $816.52：请求 $785.40、CPU $31.12；另一张截图合计 $817.14。
  [Source / 原帖](https://x.com/keking99/status/2106999400371536340)

### Sources / 来源
- [Initial voting-page report / 投票页初始报告](https://x.com/keking99/status/2106687001810677911) (source)
- [Author’s usage clarification / 作者用量补充](https://x.com/keking99/status/2106999400371536340) (source)

## levelsio: disputed Smart Shield Argo charges of about $1,500/month. / levelsio：每月约 $1,500 的 Smart Shield Argo 计费争议。

- ID: levelsio-smart-shield-argo
- Product: Smart Shield Argo
- [English page](https://billflare.dev/cases/levelsio-smart-shield-argo) · [中文页面](https://billflare.dev/zh/cases/levelsio-smart-shield-argo)
- Reported amount: ≈ $1,500
- Currency: USD; period: monthly; qualifier: approximate
- Reported cause: unknown
- Billing action: refunded; attribution: author-reported
- [Billing action source](https://x.com/levelsio/status/2044839622358794438)
- Case progress: resolved; attribution: author-reported
- Public reply archive status: staff
- Reported at: 2026-04-14
- [Original report](https://x.com/levelsio/status/2044011804628546029)

Pieter Levels says around 200 sites were charged for Smart Shield Argo although he had not enabled it. He reports about $1,500 per month and later says Cloudflare refunded everything.

Pieter Levels 称约 200 个站点未启用 Smart Shield Argo 却被收费。他报告每月约 $1,500，后称 Cloudflare 已全额退款。

On April 16, the author reported a full refund. The thread separately cites about $1,500 per month and an annual estimate of $18,000.

4 月 16 日，作者报告已全额退款。串文另提每月约 $1,500 与年度估值 $18,000。

### Timeline / 后续
- 2026-04-14: Unexpected Argo charges reported / 报告意外 Argo 费用
  The author says about 200 sites were charged for Smart Shield Argo although he had not enabled the product. / 作者称约 200 个站点未启用 Smart Shield Argo，却产生了相关费用。
  [Source / 原帖](https://x.com/levelsio/status/2044011804628546029)
- 2026-04-14: Monthly amount clarified / 补充每月金额
  The author reports charges of about $1,500 per month. / 作者报告每月约 $1,500 的费用。
  [Source / 原帖](https://x.com/levelsio/status/2044013525190746451)
- 2026-04-14: Annual estimate, not another invoice / 年度估值，不是另一张账单
  The author also cites an annual estimate of $18,000. / 作者还提及每年 $18,000 的估值。
  [Source / 原帖](https://x.com/levelsio/status/2044020998828114294)
- 2026-04-14: Personnel reply offers to look / 人员回复称会查看
  Dane Knecht replies, “Taking a look.” / Dane Knecht 回复：“我来看看。”
  [Source / 原帖](https://x.com/dok2001/status/2044029466813338087)
- 2026-04-16: Author reports a full refund / 作者称已全额退款
  The author says Cloudflare refunded everything and praises the service. / 作者称 Cloudflare 已全额退款，并称赞其服务。
  [Source / 原帖](https://x.com/levelsio/status/2044839622358794438)

### Sources / 来源
- [Original billing allegation / 原始计费指控](https://x.com/levelsio/status/2044011804628546029) (source)
- [Monthly amount in the thread / 串文中的月费](https://x.com/levelsio/status/2044013525190746451) (source)
- [Author’s estimated billing duration / 作者估计的计费时长](https://x.com/levelsio/status/2044013727956058189) (source)
- [Dane Knecht’s reply / Dane Knecht 的回复](https://x.com/dok2001/status/2044029466813338087) (staff)
- [Reply about invoice domain labels / 关于发票域名标注的回复](https://x.com/dalexeenko/status/2044028899038736464) (staff)
- [Author-reported refund / 作者报告的退款](https://x.com/levelsio/status/2044839622358794438) (source)

## Browser Rendering: an $80 report and a later correction about usage. / Browser Rendering：报告 $80，后修正对使用情况的说法。

- ID: loftwah-browser-rendering
- Product: Browser Rendering
- [English page](https://billflare.dev/cases/loftwah-browser-rendering) · [中文页面](https://billflare.dev/zh/cases/loftwah-browser-rendering)
- Reported amount: $80
- Currency: USD; period: unknown; qualifier: exact
- Reported cause: unknown
- Billing action: unknown; attribution: unknown
- Case progress: unknown; attribution: author-reported
- Public reply archive status: none
- Reported at: 2025-11-09
- [Original report](https://x.com/loftwah/status/1987626296210530512)

@loftwah initially says Browser Rendering charged $80 for services he never used, then clarifies that he had not realized he was using them. A later post says the billing issue remained unresolved.

@loftwah 最初称未使用的 Browser Rendering 产生 $80 费用，后澄清自己并不知道正在使用；再后称账单问题仍未解决。

On November 21, the author said the billing issue remained unresolved. Earlier, he changed his account from “never used” Browser Rendering to not realizing he was using it.

11 月 21 日，作者称账单问题仍未解决。此前，他将“从未使用”Browser Rendering 更正为“不知道自己正在使用”。

### Timeline / 后续
- 2025-11-09: Initial billing complaint / 首次账单抱怨
  The first located post complains about billing without giving an amount. / 目前找到的首帖抱怨计费，未给金额。
  [Source / 原帖](https://x.com/loftwah/status/1987626296210530512)
- 2025-11-09: Product and amount specified / 说明产品与金额
  The author reports an $80 Browser Rendering charge and initially says he never used the service. / 作者报告 Browser Rendering 收费 $80，最初称从未使用该服务。
  [Source / 原帖](https://x.com/loftwah/status/1987630818291068938)
- 2025-11-10: Author corrects usage context / 作者修正使用上下文
  The author clarifies that he had not realized he was using Browser Rendering. / 作者澄清自己并不知道正在使用 Browser Rendering。
  [Source / 原帖](https://x.com/loftwah/status/1987834831909323238)
- 2025-11-21: Author says issue remains unresolved / 作者称问题仍未解决
  The author says the billing issue remained unresolved on November 21. / 作者称截至 11 月 21 日账单问题仍未解决。
  [Source / 原帖](https://x.com/loftwah/status/1991717915822026958)

### Sources / 来源
- [First located billing complaint / 目前找到的首次账单抱怨](https://x.com/loftwah/status/1987626296210530512) (source)
- [Amount and product report / 金额与产品报告](https://x.com/loftwah/status/1987630818291068938) (source)
- [Author’s usage correction / 作者使用情况修正](https://x.com/loftwah/status/1987834831909323238) (source)
- [Later unresolved report / 后续未解决陈述](https://x.com/loftwah/status/1991717915822026958) (source)

## R2 replication frequency: an author reports a bill close to $100. / R2 同步频率：作者报告接近 $100 的账单。

- ID: lucianghinda-r2-replication
- Product: R2
- [English page](https://billflare.dev/cases/lucianghinda-r2-replication) · [中文页面](https://billflare.dev/zh/cases/lucianghinda-r2-replication)
- Reported amount: ≈ $100
- Currency: USD; period: unknown; qualifier: approximate
- Reported cause: writes
- Billing action: unknown; attribution: unknown
- Case progress: unknown; attribution: unknown
- Public reply archive status: none
- Reported at: 2025-08-19
- [Original report](https://x.com/lucianghinda/status/1957738066816446683)

@lucianghinda links a bill close to $100 and over 20 million R2 Class A operations to Litestream setups without a replication interval.

@lucianghinda 将接近 $100 的账单与超过 2,000 万次 R2 Class A 操作，归因于未设置同步间隔的 Litestream 配置。

The author explains that a missing replication interval caused repeated Litestream replication activity.

作者说明，遗漏同步间隔导致 Litestream 反复执行复制操作。

### Timeline / 后续
- 2025-08-19: Unexpected R2 operations reported / 报告意外 R2 操作量
  The author reports close to $100 and over 20 million Class A operations, attributing them to a forgotten Litestream replication interval. / 作者报告接近 $100 与超过 2000 万次 Class A 操作，归因于遗漏 Litestream 同步间隔。
  [Source / 原帖](https://x.com/lucianghinda/status/1957738066816446683)
- 2025-08-19: Backup context added / 补充备份上下文
  The author adds details about the Litestream backup setup. / 作者补充 Litestream 备份配置的细节。
  [Source / 原帖](https://x.com/lucianghinda/status/1957738079005122712)
- 2025-08-19: Replication explanation shared / 分享同步说明
  The author shares an explanation of the replication frequency used by Litestream. / 作者分享 Litestream 的同步频率说明。
  [Source / 原帖](https://x.com/lucianghinda/status/1957738091076284641)

### Sources / 来源
- [Original R2 operations report / 原始 R2 操作量报告](https://x.com/lucianghinda/status/1957738066816446683) (source)
- [Author explanation follow-up / 作者说明后续](https://x.com/lucianghinda/status/1957738091076284641) (source)

## MXGA: a reported $209.37 bill after a D1 query bug. / MXGA：D1 查询 bug 后报告 $209.37，作者称已豁免。

- ID: luoleiorg-mxga-d1-query
- Product: D1
- [English page](https://billflare.dev/cases/luoleiorg-mxga-d1-query) · [中文页面](https://billflare.dev/zh/cases/luoleiorg-mxga-d1-query)
- Reported amount: $209.37
- Currency: USD; period: unknown; qualifier: exact
- Reported cause: reads
- Billing action: waived; attribution: author-reported
- [Billing action source](https://x.com/luoleiorg/status/2080966064855454092)
- Case progress: resolved; attribution: author-reported
- Public reply archive status: none
- Reported at: 2026-06-30
- [Original report](https://x.com/luoleiorg/status/2071922844028764458)

@luoleiorg describes a D1 query bug that raised usage roughly 1,400-fold. An initial $200-plus report becomes $209.37 in a later post; the author says Cloudflare waived the previous month’s entire invoice after a support request.

@luoleiorg 称 D1 查询 bug 令用量升至约 1400 倍。初报 200 多刀，后给出 $209.37；作者称提交工单说明项目性质后，Cloudflare 豁免了上月整张账单。

On July 25, the author reported a waiver and clarified that it covered the entire previous-month bill, including charges beyond D1.

7 月 25 日，作者报告账单获豁免，并澄清豁免覆盖上月整张账单，不限于 D1 费用。

### Timeline / 后续
- 2026-06-30: Query bug and unexpectedly high bill / 报告查询 bug 与意外账单
  The author reports a bill above $200, including about $198 for D1, and links a 1,400-fold usage increase to a query bug. / 作者报告账单超过 $200，其中 D1 约 $198，并将约 1,400 倍的用量增长归因于查询 bug。
  [Source / 原帖](https://x.com/luoleiorg/status/2071922844028764458)
- 2026-07-25: Author reports a waiver / 作者称已豁免
  The author reports $209.37 and says a support request led to a waiver. / 作者报告 $209.37，并称提交支持工单后获得豁免。
  [Source / 原帖](https://x.com/luoleiorg/status/2080965137851351299)
- 2026-07-25: Waiver scope clarified / 补充豁免范围
  The author says the waiver covered the entire previous-month invoice, not just the database charge. / 作者称豁免的是上月整张账单，不只是数据库费用。
  [Source / 原帖](https://x.com/luoleiorg/status/2080966064855454092)

### Sources / 来源
- [Original D1 report / 原始 D1 报告](https://x.com/luoleiorg/status/2071922844028764458) (source)
- [Author-reported waiver / 作者报告的豁免](https://x.com/luoleiorg/status/2080965137851351299) (source)
- [Waiver scope follow-up / 豁免范围补充](https://x.com/luoleiorg/status/2080966064855454092) (source)

## D1 migration: the author reports a $911.56 charge after stopping the job. / D1 迁移：停止任务后，作者仍报告扣款 $911.56。

- ID: m0xandrew-d1-migration
- Product: D1
- [English page](https://billflare.dev/cases/m0xandrew-d1-migration) · [中文页面](https://billflare.dev/zh/cases/m0xandrew-d1-migration)
- Reported amount: $911.56
- Currency: USD; period: unknown; qualifier: exact
- Reported cause: writes
- Billing action: review-requested; attribution: author-reported
- [Billing action source](https://x.com/m0xandrew/status/2095437691630268457)
- Case progress: unknown; attribution: author-reported
- Public reply archive status: none
- Reported at: 2026-09-03
- [Original report](https://x.com/m0xandrew/status/2095437691630268457)

@m0xandrew says a hobby-project D1 migration reached 8,274% of a budget alert, so he stopped it and requested a one-time waiver. He later reports a $911.56 charge, closure of the old case and opening a new support case.

@m0xandrew 称爱好项目的 D1 迁移达到预算告警的 8,274%，因此停止任务并申请一次性宽限。后称扣款 $911.56、旧案关闭并新开支持工单。

The author requested one-time billing grace on September 3. On September 10, he reported a $911.56 charge, no D1 writes since September 3, migration off D1 and a new support case.

作者于 9 月 3 日申请一次性账单宽限；9 月 10 日报告已扣款 $911.56、9 月 3 日起无 D1 写入、数据库已迁离 D1，并新开工单。

### Timeline / 后续
- 2026-09-03: Migration stopped and waiver requested / 停止迁移并申请宽限
  The author says the migration reached 8,274% of a budget alert, stopped it and requested a one-time billing grace. / 作者称迁移达到预算告警的 8,274%，随后停止任务并申请一次性账单宽限。
  [Source / 原帖](https://x.com/m0xandrew/status/2095437691630268457)
- 2026-09-03: Author reports ticket closure / 作者称工单被关闭
  The author says the support agent closed the ticket and put the charge through. / 作者称支持人员关闭工单并计入费用。
  [Source / 原帖](https://x.com/m0xandrew/status/2095570511115772409)
- 2026-09-10: Invoice charge and new case reported / 报告发票扣款与新工单
  The author reports a $911.56 charge and says he opened case 02321866 after the earlier case closed before invoicing. / 作者报告扣款 $911.56，并称旧案在开票前关闭后又新开工单 02321866。
  [Source / 原帖](https://x.com/m0xandrew/status/2098106095768076526)

### Sources / 来源
- [Original D1 migration report / 原始 D1 迁移报告](https://x.com/m0xandrew/status/2095437691630268457) (source)
- [Charge and ticket follow-up / 扣款与工单跟进](https://x.com/m0xandrew/status/2098106095768076526) (source)

## mcwangcn reports past D1 write charges of “over a thousand dollars.” / mcwangcn：自述 D1 写入曾扣“上千刀”，确切金额未知。

- ID: mcwangcn-d1-writing-lessons
- Product: D1
- [English page](https://billflare.dev/cases/mcwangcn-d1-writing-lessons) · [中文页面](https://billflare.dev/zh/cases/mcwangcn-d1-writing-lessons)
- Reported amount: Not disclosed
- Currency: USD; period: unknown; qualifier: unknown
- Reported cause: writes
- Billing action: unknown; attribution: unknown
- Case progress: unknown; attribution: unknown
- Public reply archive status: none
- Reported at: 2026-10-05
- [Original report](https://x.com/mcwangcn/status/2107106092509696292)

@mcwangcn says D1 writes previously cost over a thousand dollars and separately mentions Workers CPU charges without giving an amount.

@mcwangcn 称 D1 写入曾花费上千美元，并另提 Workers CPU 费用但未给金额。

The author gives no exact D1 amount or incident date. His reference to keking99 describes another author’s case.

作者未给出 D1 的确切金额与事件日期。他提到 keking99 时描述的是另一位作者的案例。

### Timeline / 后续
- 2026-10-05: Thread of billing lessons begins / 开始讨论账单教训
  The author starts a thread about Cloudflare billing experiences. / 作者开始讨论 Cloudflare 账单经历。
  [Source / 原帖](https://x.com/mcwangcn/status/2107106092509696292)
- 2026-10-05: Past D1 write charge disclosed broadly / 粗略披露过去 D1 写入费用
  The author says D1 writes previously cost over a thousand dollars. / 作者称 D1 写入曾花费上千美元。
  [Source / 原帖](https://x.com/mcwangcn/status/2107108280464220179)
- 2026-10-05: Separate CPU-charge experience mentioned / 提及另一段 CPU 计费经历
  The author separately mentions Workers CPU charges without giving an amount. / 作者另提 Workers CPU 费用，但未给金额。
  [Source / 原帖](https://x.com/mcwangcn/status/2107153719192350915)

### Sources / 来源
- [Original billing thread / 原始账单串文](https://x.com/mcwangcn/status/2107106092509696292) (source)
- [Firsthand D1 amount range / 本人 D1 金额范围陈述](https://x.com/mcwangcn/status/2107108280464220179) (source)
- [Separate CPU context / 独立 CPU 上下文](https://x.com/mcwangcn/status/2107153719192350915) (source)

## Durable Objects: a hackathon evaluation program leads to a billing complaint. / Durable Objects：黑客松评分程序引发账单求助。

- ID: nukonuko-durable-objects-hackathon
- Product: Durable Objects
- [English page](https://billflare.dev/cases/nukonuko-durable-objects-hackathon) · [中文页面](https://billflare.dev/zh/cases/nukonuko-durable-objects-hackathon)
- Reported amount: Not disclosed
- Currency: USD; period: unknown; qualifier: unknown
- Reported cause: unknown
- Billing action: review-requested; attribution: author-reported
- [Billing action source](https://x.com/nukonuko/status/2084678833274573174)
- Case progress: unknown; attribution: author-reported
- Public reply archive status: none
- Reported at: 2026-08-04
- [Original report](https://x.com/nukonuko/status/2084674661259018477)

@nukonuko reports an unexpectedly large Cloudflare invoice, stops the suspected Durable Objects usage and asks support for a refund. Later posts link the incident to a hackathon evaluation program and say income will go toward the bill.

@nukonuko 报告 Cloudflare 意外高额账单，停止疑似 Durable Objects 用量并向支持申请退款。后续帖子将事件关联到黑客松评分程序，并称将用收入填补账单。

The author contacted support to request a refund and later said income would go toward the Cloudflare expense.

作者联系支持申请退款，后称将用收入填补 Cloudflare 费用。

### Timeline / 后续
- 2026-08-04: Unexpected invoice reported / 报告意外账单
  The author reports an unexpectedly large invoice and says he stopped the suspected Durable Objects usage. / 作者报告意外高额账单，并称已停止疑似 Durable Objects 用量。
  [Source / 原帖](https://x.com/nukonuko/status/2084674661259018477)
- 2026-08-04: Refund requested / 作者申请退款
  The author says he contacted support to ask whether a refund was possible. / 作者称已联系支持，询问是否可以退款。
  [Source / 原帖](https://x.com/nukonuko/status/2084678833274573174)
- 2026-08-09: Hackathon program identified / 关联黑客松评分程序
  The author links the expense to a July 18 hackathon evaluation program. / 作者将费用关联到 7 月 18 日的黑客松评分程序。
  [Source / 原帖](https://x.com/nukonuko/status/2086495047844040871)
- 2026-08-29: Income intended to cover expense / 作者提到用收入填补费用
  The author says income will go toward the Cloudflare expense. / 作者称将收入用于填补 Cloudflare 费用。
  [Source / 原帖](https://x.com/nukonuko/status/2093492517702660284)

### Sources / 来源
- [Original thread and follow-up / 原串与后续](https://x.com/nukonuko/status/2084674661259018477) (source)
- [Original thread and follow-up / 原串与后续](https://x.com/nukonuko/status/2084678833274573174) (source)
- [Original thread and follow-up / 原串与后续](https://x.com/nukonuko/status/2086495047844040871) (source)
- [Original thread and follow-up / 原串与后续](https://x.com/nukonuko/status/2093492517702660284) (source)

## A development app, a reported $655.83 Durable Object alarm bill. / 开发应用的 Durable Object alarm，报告账单 $655.83。

- ID: q-huy-ngo-durable-object-alarm
- Product: Durable Objects
- [English page](https://billflare.dev/cases/q-huy-ngo-durable-object-alarm) · [中文页面](https://billflare.dev/zh/cases/q-huy-ngo-durable-object-alarm)
- Reported amount: $655.83
- Currency: USD; period: unknown; qualifier: exact
- Reported cause: loop
- Billing action: review-promised; attribution: provider-reported
- [Billing action source](https://x.com/CloudflareHelp/status/2091816953635594555)
- Case progress: unknown; attribution: unknown
- Public reply archive status: responded
- Reported at: 2026-08-18
- [Original report](https://x.com/q_huy_ngo/status/2089753300329791890)

@q_huy_ngo reports a $655.83 bill and roughly 700 million interactions from a faulty alarm in an app with no users. CloudflareHelp says it will review the support case and reply in the ticket.

@q_huy_ngo 报告无用户开发应用中的 alarm 故障产生 $655.83 账单与约 7 亿次交互。CloudflareHelp 称将审查支持工单并在工单中回复。

On August 24, CloudflareHelp said it would review case 02252354 and reply in the support ticket. The author thanked the support account.

8 月 24 日，CloudflareHelp 称将审查工单 02252354，并在支持工单中回复。作者随后向支持账号道谢。

### Timeline / 后续
- 2026-08-18: Earlier billing report located / 补录更早账单报告
  The author reports a $655.83 looped Durable Object bill, a 25-day wait and an expected downgrade. This predates the previously recorded first post. / 作者报告 $655.83 Durable Object 循环账单、等待 25 天与预期降级。这早于此前收录的首帖。
  [Source / 原帖](https://x.com/q_huy_ngo/status/2089753300329791890)
- 2026-08-19: Public support request / 公开请求支持
  The author reports a $655.83 bill from a broken Durable Object alarm and says case 02252354 had been waiting for a reply for 26 days. / 作者称 Durable Object alarm 故障产生 $655.83 账单，并称工单 02252354 已等待 26 天。
  [Source / 原帖](https://x.com/q_huy_ngo/status/2089973077551784185)
- 2026-08-22: Account downgrade reported / 作者称账户被降级
  The author says the account was downgraded to Workers Free while the ticket remained under review. / 作者称账户已降级为 Workers Free，工单仍在审核。
  [Source / 原帖](https://x.com/q_huy_ngo/status/2091124195078115601)
- 2026-08-24: No billing decision reported yet / 作者称仍无账单决定
  The author says he is still waiting for a billing decision and has been downgraded to Workers Free. / 作者称仍在等待账单决定，账户已降级为 Workers Free。
  [Source / 原帖](https://x.com/q_huy_ngo/status/2091810397842182337)
- 2026-08-24: Support account promises a ticket reply / 支持账号承诺回复工单
  CloudflareHelp says it will review case 02252354 and provide feedback in the ticket. / CloudflareHelp 称将审查工单 02252354，并在工单中反馈。
  [Source / 原帖](https://x.com/CloudflareHelp/status/2091816953635594555)
- 2026-08-24: Author thanks the support account / 作者向支持账号道谢
  The author thanks CloudflareHelp for its reply. / 作者感谢 CloudflareHelp 回复。
  [Source / 原帖](https://x.com/q_huy_ngo/status/2091832690744181028)

### Sources / 来源
- [Original public support request / 原始公开求助](https://x.com/q_huy_ngo/status/2089973077551784185) (source)
- [Account downgrade update / 账户降级更新](https://x.com/q_huy_ngo/status/2091124195078115601) (source)
- [Billing decision follow-up / 账单决定跟进](https://x.com/q_huy_ngo/status/2091810397842182337) (source)
- [Official support-account reply / 官方支持账号回复](https://x.com/CloudflareHelp/status/2091816953635594555) (official)
- [Earlier billing report located / 补录更早账单报告](https://x.com/q_huy_ngo/status/2089753300329791890) (source)

## D1 row reads: an author reports a $108 bill in seven days. / D1 行读取：作者报告七天内账单 $108。

- ID: shivek-khurana-d1-reads
- Product: D1
- [English page](https://billflare.dev/cases/shivek-khurana-d1-reads) · [中文页面](https://billflare.dev/zh/cases/shivek-khurana-d1-reads)
- Reported amount: $108
- Currency: USD; period: unknown; qualifier: exact
- Reported cause: reads
- Billing action: unknown; attribution: unknown
- Case progress: unknown; attribution: unknown
- Public reply archive status: none
- Reported at: 2026-09-16
- [Original report](https://x.com/shivek_khurana/status/2100189789802959081)

@shivek_khurana reports a $108 Cloudflare D1 bill over seven days after a workflow read more rows than needed. The author says adding an index reduced reads by about 90%.

@shivek_khurana 报告工作流读取远超所需行数，Cloudflare D1 七天账单达到 $108。作者称添加索引后读取量下降约 90%。

The author says adding an index fixed the workflow and reduced reads by about 90%.

作者称添加索引修复了工作流，并使读取量下降约 90%。

### Timeline / 后续
- 2026-09-16: D1 bill and read-heavy workflow reported / 报告 D1 账单与高读取工作流
  The author reports 108 USD over seven days, attributes it to excess row reads, and says an index reduced reads by about 90%. / 作者报告七天费用为 108 USD，将其归因于过量行读取，并称添加索引后读取量下降约 90%。
  [Source / 原帖](https://x.com/shivek_khurana/status/2100189789802959081)

### Sources / 来源
- [Original D1 bill report / 原始 D1 账单报告](https://x.com/shivek_khurana/status/2100189789802959081) (source)

## shmily7: a Durable Object alarm loop and a reported $10,000 bill. / 浮世绘：Durable Object alarm 死循环，报告约一万刀账单。

- ID: shmily7-durable-object-alarm
- Product: Durable Objects
- [English page](https://billflare.dev/cases/shmily7-durable-object-alarm) · [中文页面](https://billflare.dev/zh/cases/shmily7-durable-object-alarm)
- Reported amount: ≈ $10,000
- Currency: USD; period: unknown; qualifier: approximate
- Reported cause: loop
- Billing action: declined; attribution: author-reported
- [Billing action source](https://x.com/shmily7/status/2107502590674284921)
- Case progress: unknown; attribution: author-reported
- Public reply archive status: none
- Reported at: 2026-10-06
- [Original report](https://x.com/shmily7/status/2107481028726251762)

@shmily7 reports a roughly $10,000 bill from a Durable Object alarm loop in an unused test project and later says a requested reduction was refused.

@shmily7 称无人使用的测试项目中 Durable Object alarm 陷入循环，产生约一万刀账单；后称申请减免被拒。

The author asks CloudflareHelp for a goodwill reduction, then says the amount would not be reduced and attaches a screenshot.

作者向 CloudflareHelp 请求善意减免，后称金额不会减少，并附上一张截图。

### Timeline / 后续
- 2026-10-06: Alarm-loop bill reported / 报告 alarm 循环账单
  The author reports about $10,000 in charges and six trillion reads and writes from an alarm loop in a test project. / 作者报告测试项目中的 alarm 循环产生约一万刀费用与 6 万亿次读写。
  [Source / 原帖](https://x.com/shmily7/status/2107481028726251762)
- 2026-10-06: Author discusses requesting a waiver / 作者讨论申请减免
  The author says he can apply for a one-time waiver and plans to try. / 作者称可以申请一次性减免，并打算尝试。
  [Source / 原帖](https://x.com/shmily7/status/2107483165468283109)
- 2026-10-06: Author reports payment difficulty / 作者称信用卡无力支付
  The author says his credit card cannot cover the bill. / 作者称信用卡无法支付这笔账单。
  [Source / 原帖](https://x.com/shmily7/status/2107487544741183513)
- 2026-10-06: Author adds coding-tool context / 作者补充编程工具上下文
  The author says Codex generated the code. / 作者称这段代码由 Codex 生成。
  [Source / 原帖](https://x.com/shmily7/status/2107487690023477655)
- 2026-10-06: Goodwill reduction requested publicly / 公开请求善意减免
  The author asks CloudflareHelp for a goodwill reduction, citing a one-person team and an unused test project. / 作者向 CloudflareHelp 请求善意减免，并说明团队只有一人、项目无人使用。
  [Source / 原帖](https://x.com/shmily7/status/2107502223219667018)
- 2026-10-06: Author says the reduction was refused / 作者称未获减免
  The author writes, “不肯少啊！” and attaches a screenshot. / 作者写道：“不肯少啊！”，并附上一张截图。
  [Source / 原帖](https://x.com/shmily7/status/2107502590674284921)

### Sources / 来源
- [Original Chinese report / 中文原帖](https://x.com/shmily7/status/2107481028726251762) (source)
- [Public reduction request / 公开减免请求](https://x.com/shmily7/status/2107502223219667018) (source)
- [Author-reported refusal / 作者报告的拒绝](https://x.com/shmily7/status/2107502590674284921) (source)
- [Author reports payment difficulty / 作者称信用卡无力支付](https://x.com/shmily7/status/2107487544741183513) (source)

## A simulation game, a reported $4,483.74 in Durable Object reads. / 模拟游戏的 Durable Object 读取，报告费用 $4,483.74。

- ID: songadaymann-durable-object-reads
- Product: Durable Objects
- [English page](https://billflare.dev/cases/songadaymann-durable-object-reads) · [中文页面](https://billflare.dev/zh/cases/songadaymann-durable-object-reads)
- Reported amount: $4,483.74
- Currency: USD; period: unknown; qualifier: exact
- Reported cause: reads
- Billing action: unknown; attribution: unknown
- Case progress: unknown; attribution: unknown
- Public reply archive status: staff
- Reported at: 2026-10-05
- [Original report](https://x.com/songadaymann/status/2107166770222305328)

Jonathan Mann (@songadaymann) reports spending $4,483.74 on Durable Object reads while building a simulation game. Rita Kozlov replies, “let us see what we can do”; Mann later thanks her.

Jonathan Mann（@songadaymann）称制作模拟游戏时，Durable Object 读取费用达到 $4,483.74。Rita Kozlov 回复称“看看能做些什么”，Mann 随后向她道谢。

Rita Kozlov replies, “let us see what we can do,” and Jonathan Mann later thanks her.

Rita Kozlov 回复称“看看能做些什么”，Jonathan Mann 随后向她道谢。

### Timeline / 后续
- 2026-10-05: Author reports read charges / 作者报告读取费用
  The author reports spending $4,483.74 on Durable Object reads while building a simulation game. / 作者称制作模拟游戏时，Durable Object 读取费用达到 $4,483.74。
  [Source / 原帖](https://x.com/songadaymann/status/2107166770222305328)
- 2026-10-05: Rita Kozlov replies / Rita Kozlov 回复
  Rita Kozlov replies, “let us see what we can do.” / Rita Kozlov 回复称：“看看能做些什么。”
  [Source / 原帖](https://x.com/ritakozlov/status/2107168559759757431)
- 2026-10-05: Author thanks the responder / 作者向回复者道谢
  The author thanks Rita. / 作者向 Rita 道谢。
  [Source / 原帖](https://x.com/songadaymann/status/2107168724176257256)
- 2026-10-05: Author adds usual-bill context / 作者补充平时账单情况
  The author says his Cloudflare bills are usually low and describes the service as easier to use with LLMs than Vercel and Supabase. / 作者称自己平时的 Cloudflare 账单较低，并说 Cloudflare 与 LLM 配合使用比 Vercel 和 Supabase 更容易。
  [Source / 原帖](https://x.com/songadaymann/status/2107191083537195495)

### Sources / 来源
- [Original report and video / 原始报告与视频](https://x.com/songadaymann/status/2107166770222305328) (source)
- [Rita Kozlov’s response / Rita Kozlov 的回应](https://x.com/ritakozlov/status/2107168559759757431) (staff)
- [Author’s thank-you / 作者道谢](https://x.com/songadaymann/status/2107168724176257256) (source)
- [Author’s later context / 作者后续补充](https://x.com/songadaymann/status/2107191083537195495) (source)

## Standard Agents: two loops, a reported $8,846 bill. / Standard Agents：两个死循环，报告账单 $8,846。

- ID: standard-agents-durable-objects
- Product: Durable Objects
- [English page](https://billflare.dev/cases/standard-agents-durable-objects) · [中文页面](https://billflare.dev/zh/cases/standard-agents-durable-objects)
- Reported amount: $8,846
- Currency: USD; period: unknown; qualifier: exact
- Reported cause: loop
- Billing action: adjusted; attribution: author-reported
- [Billing action source](https://x.com/jpschroeder/status/2089436181666668764)
- Case progress: resolved; attribution: author-reported
- Public reply archive status: staff
- Reported at: 2026-08-08
- [Original report](https://x.com/jpschroeder/status/2086144942657712500)

Justin Schroeder and Boyd describe the same Standard Agents incident: two Durable Objects ran unbounded loops. Justin reports an $8,846 bill and a later bill adjustment.

Justin Schroeder 与 Boyd 描述同一宗 Standard Agents 事件：两个 Durable Objects 运行了无终止循环。Justin 报告账单 $8,846，后称账单已调整。

On August 17, Justin reported that Cloudflare adjusted the $8,846 bill.

8 月 17 日，Justin 称 Cloudflare 调整了 $8,846 账单。

### Timeline / 后续
- 2026-08-08: Boyd reports the same runaway process / Boyd 首次报告同一循环事件
  Boyd reports a runaway process in two Durable Objects and asks how to stop services beyond intended limits. His post begins the grouped Standard Agents incident. / Boyd 报告两个 Durable Objects 出现失控进程，并询问如何停止超出预期额度的服务。该帖是 Standard Agents 事件的早期报告。
  [Source / 原帖](https://x.com/0xBOYD/status/2086136894803279932)
- 2026-08-08: Boyd describes the first billing alert / Boyd 描述首次账单告警
  Boyd says this was their first billing alert and first time exceeding the threshold. His report describes the same Standard Agents incident as Justin’s. / Boyd 称这是团队首次收到账单告警，也是首次超过阈值。他的报告描述了 Justin 所说的同一宗 Standard Agents 事件。
  [Source / 原帖](https://x.com/0xBOYD/status/2086139185086243046)
- 2026-08-08: Justin reports the bill / Justin 报告账单
  Justin links the $8,846 bill to loops in two Durable Objects and acknowledges his code. / Justin 将 $8,846 账单与两个 Durable Objects 中的循环关联，并承认代码由他编写。
  [Source / 原帖](https://x.com/jpschroeder/status/2086144942657712500)
- 2026-08-08: More context in the original thread / 原串补充上下文
  Justin adds context in the original thread. / Justin 在原串中补充上下文。
  [Source / 原帖](https://x.com/jpschroeder/status/2086154004015288386)
- 2026-08-08: Limits and alerts mentioned in a reply / 人员回复提到限制与告警
  Dane Knecht replies, “Limits and alerts coming.” / Dane Knecht 回复：“即将推出限制与告警。”
  [Source / 原帖](https://x.com/dok2001/status/2086157300339708266)
- 2026-08-13: Author says card was charged / 作者称信用卡已扣款
  The author says Cloudflare charged the full amount and the support ticket had no reply. The later adjustment remains a separate follow-up. / 作者称已扣全额且工单尚无回复。后续账单调整保留为独立进展。
  [Source / 原帖](https://x.com/jpschroeder/status/2087866702327370068)
- 2026-08-17: Author reports a bill adjustment / 作者称账单已调整
  Justin reports a bill adjustment in a follow-up to the original incident. / Justin 在关联原事件的后续帖中称账单已调整。
  [Source / 原帖](https://x.com/jpschroeder/status/2089436181666668764)
- 2026-08-19: Reply acknowledges help / 回复确认提供过协助
  Dmitry Alexeenko replies that Cloudflare was able to help. / Dmitry Alexeenko 回复称 Cloudflare 已提供协助。
  [Source / 原帖](https://x.com/dalexeenko/status/2090024941240410418)

### Sources / 来源
- [Justin’s original report / Justin 原帖](https://x.com/jpschroeder/status/2086144942657712500) (source)
- [Boyd’s report of the same incident / Boyd 对同一事件的报告](https://x.com/0xBOYD/status/2086136894803279932) (source)
- [Boyd: alert coverage / Boyd：告警覆盖说明](https://x.com/0xBOYD/status/2086143037042749480) (source)
- [Boyd: additional alert context / Boyd：告警补充](https://x.com/0xBOYD/status/2086229863812202970) (source)
- [Boyd says Cloudflare is looking into it / Boyd 称 Cloudflare 正在查看](https://x.com/0xBOYD/status/2086158466624721230) (source)
- [Boyd references Justin’s report / Boyd 引用 Justin 的报告](https://x.com/0xBOYD/status/2086539168197292178) (source)
- [Dane Knecht: limits and alerts reply / Dane Knecht：限制与告警回复](https://x.com/dok2001/status/2086157300339708266) (staff)
- [Contact reply using a Cloudflare email / 使用 Cloudflare 邮箱的联系回复](https://x.com/dalexeenko/status/2086150144488042858) (staff)
- [Follow-up contact reply / 后续联系回复](https://x.com/dalexeenko/status/2086215157957407140) (staff)
- [Author-reported adjustment / 作者报告的账单调整](https://x.com/jpschroeder/status/2089436181666668764) (source)
- [Author says card was charged / 作者称信用卡已扣款](https://x.com/jpschroeder/status/2087866702327370068) (source)

## Will Moss: a reported 20 trillion Durable Object reads from an alarm loop. / Will Moss：alarm 循环报告约 20 万亿次读取，估计费用超过三万刀。

- ID: willmoss-durable-object-alarm
- Product: Durable Objects
- [English page](https://billflare.dev/cases/willmoss-durable-object-alarm) · [中文页面](https://billflare.dev/zh/cases/willmoss-durable-object-alarm)
- Reported amount: Not disclosed
- Currency: USD; period: unknown; qualifier: unknown
- Reported cause: loop
- Billing action: unknown; attribution: unknown
- Case progress: unknown; attribution: unknown
- Public reply archive status: none
- Reported at: 2026-04-16
- [Original report](https://x.com/itswillmoss/status/2044797874500681751)

@itswillmoss reports 20,213,871,155,804 Durable Object reads, a dashboard mismatch and lost project access. He attributes the loop to health checks waking onStart and repeatedly setting an alarm. The X thread estimates the cost above $30,000.

@itswillmoss 报告 20,213,871,155,804 次 Durable Object 读取、仪表盘数字不符与项目访问中断。他将循环归因于健康检查唤醒 onStart 后反复设置 alarm。X 串文估计费用超过 $30,000。

The author says he opened a support case immediately after receiving the invoice and estimates the cost above $30,000.

作者称收到发票后立即提交支持工单，并估计费用超过 $30,000。

### Timeline / 后续
- 2026-04-16: Unexpected read count reported / 报告意外读取次数
  The author reports about 20.2 trillion Durable Object reads on the invoice. / 作者报告发票上约 20.2 万亿次 Durable Object 读取。
  [Source / 原帖](https://x.com/itswillmoss/status/2044797874500681751)
- 2026-04-16: Lost access and support case reported / 报告访问中断与工单
  The author says Workers Paid was disabled, the project became unavailable and a support case was opened immediately. / 作者称 Workers Paid 被关闭，项目不可用，并已立即提交支持工单。
  [Source / 原帖](https://x.com/itswillmoss/status/2044797876614652178)
- 2026-04-16: Dashboard and alerts questioned / 质疑仪表盘与告警
  The author says the dashboard did not reflect the invoice’s count and there was no excess-usage notification. / 作者称仪表盘未显示发票中的用量，也没有超额通知。
  [Source / 原帖](https://x.com/itswillmoss/status/2044797878720196851)
- 2026-04-16: Alarm diagnosis described / 说明 alarm 诊断
  The author says health checks woke the object every 60 seconds and onStart set an alarm without checking getAlarm. / 作者称健康检查每 60 秒唤醒对象，onStart 未先检查 getAlarm 就设置 alarm。
  [Source / 原帖](https://x.com/itswillmoss/status/2044797884080730203)
- 2026-04-16: Cost described as an estimate / 将费用表述为估算
  The author estimates that the cost may exceed $30,000. / 作者估计费用可能超过 $30,000。
  [Source / 原帖](https://x.com/itswillmoss/status/2044797885846286374)

### Sources / 来源
- [Original read-count report / 原始读取次数报告](https://x.com/itswillmoss/status/2044797874500681751) (source)
- [Dashboard count comparison / 仪表盘数字对比](https://x.com/itswillmoss/status/2044797881014464549) (source)
- [Cost estimate, not invoice total / 费用估算，不是发票总额](https://x.com/itswillmoss/status/2044797885846286374) (source)

## D1 status writes: an author reports a 150-dollar charge and refund. / D1 状态定时写入：作者报告 150 刀费用，后称已退款。

- ID: wofuhuola-d1-status-writes
- Product: D1
- [English page](https://billflare.dev/cases/wofuhuola-d1-status-writes) · [中文页面](https://billflare.dev/zh/cases/wofuhuola-d1-status-writes)
- Reported amount: $150
- Currency: USD; period: monthly; qualifier: exact
- Reported cause: writes
- Billing action: refunded; attribution: author-reported
- [Billing action source](https://x.com/wofuhuola/status/2107032486064914901)
- Case progress: resolved; attribution: author-reported
- Public reply archive status: none
- Reported at: 2026-10-05
- [Original report](https://x.com/wofuhuola/status/2107032486064914901)

@wofuhuola describes a generated tool writing Reddit post statuses globally every five minutes and deleting expired rows. The author says one month cost 150 dollars, went unnoticed for three months, and was later refunded after an appeal.

@wofuhuola 称生成的小工具每 5 分钟全局写入 Reddit 帖子状态并删除过期行，一个月产生 150 刀费用，三个月后才发现；作者称申诉后获退款。

The author says he discovered the $150 monthly D1 charge three months later and that Cloudflare returned the money after his appeal.

作者称三个月后发现每月 $150 的 D1 费用，并称 Cloudflare 在其申诉后退还了款项。

### Timeline / 后续
- 2026-10-05: Writes, charge and refund reported together / 同时报告写入费用与退款
  The author says his tool wrote Reddit post statuses every five minutes, generating a $150 D1 charge in one month. He discovered it three months later and reports that Cloudflare returned the money after an appeal. / 作者称工具每 5 分钟写入 Reddit 帖子状态，一个月产生 $150 D1 费用。他三个月后发现账单，并称 Cloudflare 在申诉后退还款项。
  [Source / 原帖](https://x.com/wofuhuola/status/2107032486064914901)
- 2026-10-05: Author thanks Cloudflare / 作者称赞 Cloudflare
  The author praises Cloudflare after reporting the refund. / 作者报告退款后继续称赞 Cloudflare。
  [Source / 原帖](https://x.com/wofuhuola/status/2107033296211476631)

### Sources / 来源
- [First located firsthand account / 目前找到的第一人称陈述](https://x.com/wofuhuola/status/2107032486064914901) (source)
- [Author follow-up / 作者后续](https://x.com/wofuhuola/status/2107033296211476631) (source)


## Read more
- [index.md](https://billflare.dev/agents/index.md)
- [categories.md](https://billflare.dev/agents/categories.md)
- [tags.md](https://billflare.dev/agents/tags.md)
- [collections.md](https://billflare.dev/agents/collections.md)
- [cases.md](https://billflare.dev/agents/cases.md)
- [guides.md](https://billflare.dev/agents/guides.md)
- [submit.md](https://billflare.dev/agents/submit.md)
- [methodology.md](https://billflare.dev/agents/methodology.md)
- [about.md](https://billflare.dev/agents/about.md)
- [llms.txt](https://billflare.dev/llms.txt)
- [llms-full.txt](https://billflare.dev/llms-full.txt)

# Billflare billing guides / 计费避坑指南

## Budget alerts / 预算预警

- ID: cloudflare-budget-alerts; kind: official-docs
- [English page](https://billflare.dev/guides/cloudflare-budget-alerts) · [中文页面](https://billflare.dev/zh/guides/cloudflare-budget-alerts)
- Source: Cloudflare Docs / Cloudflare 开发者文档
- Products: Account-wide usage-based products
- [Original source](https://developers.cloudflare.com/billing/manage/budget-alerts/)

Cloudflare documents account-wide spend alerts and their notification limits.

Cloudflare 官方说明账号级费用预警及其通知边界。

- The alert tracks cumulative usage-based spend across the account during the current billing period, then emails the configured recipients after the threshold is crossed. / 预警累计当前账期的账号级用量计费支出；越过设定阈值后，系统向指定收件人发送邮件。
- It sends one notification after crossing the threshold and resets for the next billing period. It does not pause or cap usage; the invoice remains authoritative. / 越过阈值后，预警发送一次通知，并在下个账期重置。它不暂停或限制用量；最终费用以账单为准。
- Cloudflare lists Budget alerts for Pay-as-you-go accounts, not Enterprise contracts. / Cloudflare 将预算预警列为按量付费账号功能，不适用于 Enterprise 合约。

### Thread and updates / 串文与更新

## Cloudflare cost playbook / Cloudflare 成本 Playbook

- ID: cloudflare-cost-playbook; kind: community-resource
- [English page](https://billflare.dev/guides/cloudflare-cost-playbook) · [中文页面](https://billflare.dev/zh/guides/cloudflare-cost-playbook)
- Source: GitHub repository / GitHub 仓库
- Author: KurosawaGeeker / KurosawaGeeker
- Products: Workers, R2
- [Original source](https://github.com/KurosawaGeeker/cloudflare-cost-playbook)

A community playbook for Cloudflare cost retrospectives, cost models, and code review.

围绕 Cloudflare 成本复盘、费用模型与代码审查的社区手册。

- The repository combines incident retrospectives with agent review rules for request paths, polling, caching, and billing alerts. / 仓库把事故复盘与 Agent 审查规则结合，要求检查请求路径、轮询、缓存和账单预警。
- Its calculator distinguishes direct public R2 reads from Worker-proxied reads. A cache hit can avoid an R2 read but still invoke a Worker; the model covers selected Workers and R2 usage, not the whole bill. / 计算器区分直接读取公开 R2 与经 Worker 代理的读取。缓存命中可避免 R2 读取，但仍会调用 Worker；模型只覆盖部分 Workers 与 R2 用量，不代表整张账单。
- The repository provides review material and a calculator template, not a hosted service or a hard spending cap. / 仓库提供审查资料与计算器模板，不提供托管服务或费用硬上限。

### Thread and updates / 串文与更新

## Workers limits / Workers 限制

- ID: cloudflare-workers-limits; kind: official-docs
- [English page](https://billflare.dev/guides/cloudflare-workers-limits) · [中文页面](https://billflare.dev/zh/guides/cloudflare-workers-limits)
- Source: Cloudflare Docs / Cloudflare 开发者文档
- Products: Workers
- [Original source](https://developers.cloudflare.com/workers/platform/limits/)

Cloudflare lists account and invocation limits for Workers.

Cloudflare 官方列出 Workers 账号与单次调用限制。

- CPU time measures Worker execution, not time waiting for fetch, KV, or database responses. / CPU 时间统计 Worker 执行时间，不统计等待 fetch、KV 或数据库响应的时间。
- For HTTP requests, the documented CPU limit is 10 ms on Free and 30 seconds by default on Paid, with a configurable maximum of five minutes. / HTTP 请求的 CPU 限制为 Free 方案 10 毫秒、Paid 方案默认 30 秒，最高可调至 5 分钟。
- Paid CPU limits can be set with Wrangler's limits.cpu_ms or in Dashboard > Workers & Pages > a Worker > Settings. These per-invocation limits do not cap account spend. / Paid 方案可用 Wrangler 的 limits.cpu_ms 或 Dashboard > Workers & Pages > Worker > Settings 设置 CPU 限制。该单次调用限制不封顶账号费用。

### Thread and updates / 串文与更新

## D1 billing incident and circuit breakers / D1 计费事故与熔断复盘

- ID: d1-billing-circuit-breakers; kind: author-experience
- [English page](https://billflare.dev/guides/d1-billing-circuit-breakers) · [中文页面](https://billflare.dev/zh/guides/d1-billing-circuit-breakers)
- Source: Little Bear Apps / Little Bear Apps
- Author: Nathan Schram / Nathan Schram
- Products: D1, Workers
- [Original source](https://littlebearapps.com/blog/d1-billing-disaster-circuit-breakers/)

Nathan Schram describes D1 write risks and circuit-breaker approaches.

Nathan Schram 介绍 D1 写入风险与熔断方式。

- The author describes duplicate work in an embedder and a harvester that reinserted existing rows. He recommends deduplication and INSERT ... ON CONFLICT DO UPDATE for repeated records. / 作者描述了嵌入器重复工作，以及采集器重复插入旧行的问题；他建议增加去重，并用 INSERT ... ON CONFLICT DO UPDATE 更新重复记录。
- His breakers have three scopes: a feature budget for each function in a project, a project budget that aggregates its features, and a global emergency stop across projects. / 作者设计了三层熔断：项目内每项功能有独立预算；项目预算汇总各功能；全局紧急停止覆盖所有项目。
- The article describes operation-count monitoring through wrapped bindings and a Queue-to-Analytics-Engine path, so monitoring does not add D1 writes. A budget check runs about every 30 seconds. / 文章以包装后的绑定统计操作次数，再经 Queue 写入 Analytics Engine，避免监控本身增加 D1 写入；预算约每 30 秒检查一次。

### Thread and updates / 串文与更新

## WebSocket hibernation with Durable Objects / Durable Objects WebSocket 休眠

- ID: durable-objects-websocket-hibernation; kind: official-docs
- [English page](https://billflare.dev/guides/durable-objects-websocket-hibernation) · [中文页面](https://billflare.dev/zh/guides/durable-objects-websocket-hibernation)
- Source: Cloudflare Docs / Cloudflare 开发者文档
- Products: Durable Objects
- [Original source](https://developers.cloudflare.com/durable-objects/examples/websocket-hibernation-server/)

Cloudflare shows how Durable Objects hibernate WebSocket connections while idle.

Cloudflare 官方示例说明 Durable Objects 如何让闲置 WebSocket 连接休眠。

- A Durable Object calls ctx.acceptWebSocket for a server-side socket. When idle, the object can leave memory while the WebSocket connection remains open; a later message recreates the object. / Durable Object 对服务端 WebSocket 调用 ctx.acceptWebSocket。对象闲置时可退出内存，连接仍保持打开；后续消息会重建对象。
- In its constructor, the example retrieves hibernating sockets and restores per-connection state from serialized attachments. / 示例在构造函数中取回休眠中的 WebSocket，并从序列化附件恢复每条连接的状态。
- Hibernation applies only when the Durable Object acts as the WebSocket server; it does not support outbound WebSocket connections. / 只有 Durable Object 作为 WebSocket 服务端时才支持休眠；出站 WebSocket 连接不支持。

### Thread and updates / 串文与更新

## Cloudflare billing pitfalls thread / Cloudflare 计费避坑指南串文

- ID: mcwangcn-billing-thread; kind: author-experience
- [English page](https://billflare.dev/guides/mcwangcn-billing-thread) · [中文页面](https://billflare.dev/zh/guides/mcwangcn-billing-thread)
- Source: 𝕏 / 𝕏
- Author: yvonuk (@mcwangcn) / yvonuk（@mcwangcn）
- Products: Workers, D1, Durable Objects, Email Sending, Containers
- [Original source](https://x.com/mcwangcn/status/2107106092509696292)

The author organizes Cloudflare billing risks by product and shares experience with budget alert emails.

作者按产品整理 Cloudflare 计费风险，并补充预算预警的使用经验。

- The author covers D1, Durable Objects, Workers, Email Sending, and Containers in five numbered posts. / 作者用五篇编号帖子介绍 D1、Durable Objects、Workers、Email Sending 与 Containers。
- The thread links billing risks to full-table writes, request and CPU usage, bot-triggered email, and separate container charges. / 串文分别讨论全表写入、请求与 CPU 用量、机器人触发邮件及独立容器费用。
- A later post adds the author’s experience with delayed budget-alert emails. All collected nodes and their original text appear below. / 后续帖子补充作者遇到预算预警邮件延迟的经历。下方按顺序保留收录节点与原文。

### Thread and updates / 串文与更新
- 2026-10-05: [D1: the author warns that full-table UPDATE statements grow write volume as tables expand, especially when linked to requests. / D1：作者提醒，全表 UPDATE 会随表增长扩大写入量，尤其是与请求绑定时。](https://x.com/mcwangcn/status/2107108280464220179)
- 2026-10-05: [Durable Objects: the author highlights database and request usage as separate billing concerns. / Durable Objects：作者提醒关注数据库用量与请求用量的计费。](https://x.com/mcwangcn/status/2107110284070445346)
- 2026-10-05: [Workers: the author separates request charges from CPU-time charges and describes experience with CPU costs. / Workers：作者区分请求计费与 CPU 时间计费，并提到自己的 CPU 费用经历。](https://x.com/mcwangcn/status/2107153719192350915)
- 2026-10-05: [Email Sending: the author describes bot sign-ups amplifying email usage on a magic-link login flow. / Email Sending：作者描述机器人注册放大 magic link 登录邮件用量。](https://x.com/mcwangcn/status/2107158429831762199)
- 2026-10-05: [Containers: the author explains that container charges are separate from the Workers Paid subscription and reports idle costs from a personal test. / Containers：作者提醒容器费用独立于 Workers Paid 订阅，并介绍自己的闲置测试费用。](https://x.com/mcwangcn/status/2107160249182695729)
- 2026-10-07: [Budget alerts: the author reports emails arriving hours or a day after unexpected usage. / 预算预警：作者报告邮件曾在异常用量发生数小时或一天后才到达。](https://x.com/mcwangcn/status/2107747935718887900)


## Read more
- [index.md](https://billflare.dev/agents/index.md)
- [categories.md](https://billflare.dev/agents/categories.md)
- [tags.md](https://billflare.dev/agents/tags.md)
- [collections.md](https://billflare.dev/agents/collections.md)
- [cases.md](https://billflare.dev/agents/cases.md)
- [guides.md](https://billflare.dev/agents/guides.md)
- [submit.md](https://billflare.dev/agents/submit.md)
- [methodology.md](https://billflare.dev/agents/methodology.md)
- [about.md](https://billflare.dev/agents/about.md)
- [llms.txt](https://billflare.dev/llms.txt)
- [llms-full.txt](https://billflare.dev/llms-full.txt)

# Contribute to Billflare / 提供案例与指南

Submit a public source through the GitHub Issue Form. Contributions are reviewed before updating the public snapshot.
通过 GitHub Issue Form 提交公开来源。人工审核后更新公开快照，不自动发布。

- [Submit a source](https://github.com/daftAI2026/billflare-reports/issues/new?template=report-en.yml)
- [提供案例](https://github.com/daftAI2026/billflare-reports/issues/new?template=report-zh.yml)

Include the original public URL and the author’s thread, replies or follow-ups. Keep one incident or guide thread together.
附上原始公开链接和作者串文、回复或后续。同一事件或指南串文归并为一条。
Issue submissions are public. Do not include private account details, payment information, passwords or API keys.
Issue 投稿内容公开。不要提交私人账户、支付信息、密码或 API Key。

## Read more
- [index.md](https://billflare.dev/agents/index.md)
- [categories.md](https://billflare.dev/agents/categories.md)
- [tags.md](https://billflare.dev/agents/tags.md)
- [collections.md](https://billflare.dev/agents/collections.md)
- [cases.md](https://billflare.dev/agents/cases.md)
- [guides.md](https://billflare.dev/agents/guides.md)
- [submit.md](https://billflare.dev/agents/submit.md)
- [methodology.md](https://billflare.dev/agents/methodology.md)
- [about.md](https://billflare.dev/agents/about.md)
- [llms.txt](https://billflare.dev/llms.txt)
- [llms-full.txt](https://billflare.dev/llms-full.txt)

# Billflare collection policy / 收录原则

## How we collect cases

We organize public billing reports and follow-ups. We do not audit private accounts or adjudicate billing disputes.

### Trace the original report.

A case needs a public original source describing an unexpected Cloudflare charge. We group the author’s thread, replies and follow-ups into one incident. Reposts are leads, not additional cases.

### Distinguish charges from estimates.

We preserve the reported number and stated billing period. An estimate is marked ≈; an undisclosed amount stays unknown, not zero. Cloudflare reports using $ default to USD unless the source states otherwise. Monthly costs stay monthly. The case directory sums recorded report amounts, not net losses; refunds do not subtract from the reported charge.

### Identify who reported it.

We check that links, quoted text and incident identity match their sources. Author-reported and provider-reported identify who stated an outcome, not a trust score. We do not verify private invoices or refund settlement. A source that explicitly contradicts an earlier statement is retained as a correction or conflicting account, with both links.

### Keep the reported explanation.

Cause tags organize explanations found in the original reports. We attribute each explanation to its author rather than present it as our technical diagnosis. Corrections stay in the same incident’s timeline.

### Record the specific follow-up.

Each update links to its original source. We distinguish refunds, waivers, credits, adjustments, declined requests and ongoing review, with author or provider attribution. Public replies are recorded separately. An author-reported refund remains visible even when no public provider reply is linked. Partial outcomes retain their stated scope, and a thank-you is recorded as a thank-you.

- [Collection policy](https://billflare.dev/methodology)

## 我们怎样收录案例

整理公开账单报告与后续，不审计私人账单，不裁决账单争议。

### 先找到原始报告。

案例需要公开原始来源，说明当事人遇到的 Cloudflare 意外费用。作者的串文、回复和后续归并为同一事件。转述只作线索，不重复计为案例。

### 分清账单与估算。

保留报告数字和已注明的账期。估算标记为 ≈，未披露金额保持未知，不填零。Cloudflare 报告中的 $ 和“刀”默认按 USD 展示，原帖明确其他币种时除外。月费保持月费。案例目录合计是已记录报告金额之和，不是净损失；退款不扣减原报告费用。

### 说明是谁报告的。

我们检查链接、原文和事件归并是否对应。“作者报告”和“平台报告”说明陈述来源，不是可信度评级。本站不独立审计私人账单或核验退款到账。后续来源明确纠正或反驳早期陈述时，保留更正内容与双方链接。

### 保留原帖中的原因说明。

原因标签整理原帖给出的解释，注明是谁提出的，不作为本站技术诊断。作者后续更正原因时，在同一案例时间线中保留更新。

### 记录具体后续动作。

每条更新链接自己的原始来源。退款、减免、抵扣、调整、拒绝和复核进展分别记录，并标明作者或平台报告。公开回复另列；尚未收录公开回复，不影响展示作者报告的退款。部分结果保留原帖说明的范围，感谢帖只记录感谢。

- [收录原则](https://billflare.dev/zh/methodology)


## Read more
- [index.md](https://billflare.dev/agents/index.md)
- [categories.md](https://billflare.dev/agents/categories.md)
- [tags.md](https://billflare.dev/agents/tags.md)
- [collections.md](https://billflare.dev/agents/collections.md)
- [cases.md](https://billflare.dev/agents/cases.md)
- [guides.md](https://billflare.dev/agents/guides.md)
- [submit.md](https://billflare.dev/agents/submit.md)
- [methodology.md](https://billflare.dev/agents/methodology.md)
- [about.md](https://billflare.dev/agents/about.md)
- [llms.txt](https://billflare.dev/llms.txt)
- [llms-full.txt](https://billflare.dev/llms-full.txt)

# About Billflare / 关于 Billflare

## About Billflare

An independent archive of unexpected Cloudflare bills and what happened next.

### Understand the bill, follow the outcome.

Each case brings together the reported charge, affected product, original sources and follow-ups. Read the author’s account and follow what happened next.

### Billing incidents, not general cloud news.

We focus on unexpected Cloudflare charges. Reposts, pricing examples, and reports about other providers are not separate Cloudflare cases. Related updates belong to the same incident.

### Independent and unofficial.

Billflare is not affiliated with Cloudflare. Inclusion does not establish fault. We do not access your account, monitor your spending, or provide refunds or billing support.

### Help complete the record.

Reports go to a public GitHub form and are reviewed before inclusion. Send original sources for a new case, a follow-up, or a correction. Do not share account numbers, payment details, or secrets.

- [About](https://billflare.dev/about)

## 关于 Billflare

一个记录 Cloudflare 意外账单及其后续的独立案例库。

### 看清账单，追踪后续。

每个案例汇集报告金额、涉及产品、原始来源和后续帖文。你可以回到原帖，阅读当事人陈述，追踪事情后续。

### 聚焦意外账单，不做泛云新闻。

我们关注 Cloudflare 意外费用。转述、定价示例和其他云服务的账单不单独算作 Cloudflare 案例。同一事件的串文与后续归入同一份档案。

### 独立、非官方。

Billflare 与 Cloudflare 无关联。收录不等于责任认定。我们不接入你的账户、不监控你的支出，也不提供退款或账单客服服务。

### 一起补全档案。

案例通过公开 GitHub 表单提交，审核后再收录。新案例、后续进展和纠错都需要原始来源。请勿公开账户编号、支付信息或密钥。

- [关于](https://billflare.dev/zh/about)


## Read more
- [index.md](https://billflare.dev/agents/index.md)
- [categories.md](https://billflare.dev/agents/categories.md)
- [tags.md](https://billflare.dev/agents/tags.md)
- [collections.md](https://billflare.dev/agents/collections.md)
- [cases.md](https://billflare.dev/agents/cases.md)
- [guides.md](https://billflare.dev/agents/guides.md)
- [submit.md](https://billflare.dev/agents/submit.md)
- [methodology.md](https://billflare.dev/agents/methodology.md)
- [about.md](https://billflare.dev/agents/about.md)
- [llms.txt](https://billflare.dev/llms.txt)
- [llms-full.txt](https://billflare.dev/llms-full.txt)