Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
lofteryang: a duplicate $160 charge.
Community user lofteryang says a payment for tokomi.ai was charged twice and asks for one $160 charge to be refunded; the first PayPal attempt showed as failed before a second method succeeded.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2026-09-01
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author asks for one $160 charge to be refunded. A community MVP links the ticket guide.
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 post includes a PayPal transaction reference dated September 1, 2026. A community MVP says billing issues need a support ticket.
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.
Meathill: OpenNext KV ISR cache left unpaid TTL work and ballooned storage.
Meathill reports that an OpenNext Cloudflare KV incremental-cache path for Next.js ISR left a TODO for KV TTL, so versioned page snapshots accumulated. Dashboard billable storage showed 3.59 GB-month over the 1 GB free allowance with ongoing extra charges, and historical zombie data reached about 24 GB before he moved to a new namespace. He does not state a dollar invoice total.
Budget alerts
Cloudflare documents account-wide spend alerts and their notification limits.