BREAKING: Cloudflare MINOR ⚠️ Durable Objects count discrepancies [kv8v7ymsglkc]

Cloudflare Durable Objects experiencing reported count discrepancies. Immediate workarounds for indie hackers inside.

BREAKING: Cloudflare Durable Objects Count Discrepancies ⚠️

Status: Identified | Severity: MINOR | Impact: Partial

---

What's Down & Who's Affected

Cloudflare is reporting Durable Objects count discrepancies in their billing and analytics dashboards. This affects:

Dashboard reporting: Object counts may not reflect actual instances

Billing accuracy: Reported usage numbers may be inaccurate (you're still being billed correctly—this is display-side)

Analytics: Historical data queries may show wrong totals

Affected regions: Global impact on Durable Objects metrics

Who this hits hardest:

Teams using Durable Objects for production state management

Projects relying on cost monitoring via Cloudflare dashboard

High-volume DO deployments (100+ objects)

Current status: No service disruption. Your Durable Objects are running normally. This is a metrics/reporting issue only.

---

Immediate Workarounds (RIGHT NOW)

1. Trust Your Logs, Not the Dashboard

``` Use Cloudflare Logpush or Workers Analytics to verify actual DO usage. Don't rely on dashboard counters until resolved. ```

2. Enable Logpush Immediately (if available on your plan)

Route: Cloudflare Dashboard → Logs → Logpush

Export to: Datadog, Sumo Logic, or S3

Get authoritative usage data outside the broken dashboard

3. Query via API

```bash

Use Cloudflare API to fetch zone analytics directly

curl -X GET "https://api.cloudflare.com/client/v4/zones/{zone_id}/analytics/workers/invocations" \ -H "Authorization: Bearer {token}" ``` API endpoints may have more reliable counts than the UI.

4. Implement Client-Side Counting

```javascript // Add DO instantiation logging in your Workers script const do_count = new Map(); // Track IDs of created objects locally // Post to external service for independent verification ```

5. Pause Billing Alerts (Temporarily)

Disable cost notifications if you have them—they may fire incorrectly based on bad dashboard data. Re-enable once Cloudflare confirms resolution.

---

How to Check If Your Project Is Affected

1. Go to: Cloudflare Dashboard → Workers → Durable Objects 2. Look for: Numbers that seem off (sudden spikes, unexplained drops) 3. Cross-reference: Check your application logs for actual object creation/deletion events 4. Red flags: - Dashboard shows 0 objects but you're getting billed - Count changes without corresponding code deployments - Historical charts show gaps or inconsistencies

If your numbers don't match your app logic: you're likely affected.

---

Alternative Tools to Consider

| Tool | Use Case | Status | |------|----------|--------| | AWS DynamoDB | Drop-in global state replacement | ✅ Independent | | Supabase Realtime | Collaborative state + auth | ✅ Independent | | Redis Enterprise Cloud | Fast K/V + Lua scripting | ✅ Independent | | Fauna | Serverless database with transactions | ✅ Independent |

Don't migrate yet. This is minor and identified. Wait 24-48 hours before considering alternatives.

---

Monitor Recovery

Check these sources:

1. Cloudflare Status Page: https://www.cloudflarestatus.com/ - Subscribe to Durable Objects incident updates

2. Set up notifications for the incident ticket

3. Re-check dashboard in 2-4 hours (typical resolution window for metrics issues)

4. Verify via API once Cloudflare posts "resolved" status

---

Bottom Line

Your Durable Objects are working. Your billing is accurate. Your dashboard metrics are lying. Use API/logs for truth until fixed. No action required unless you're actively troubleshooting costs.

ETA on fix: Cloudflare typically resolves metrics issues within 4-6 hours.

Stay calm. Keep building. 🚀