Billing, platform status, and CloudBlog

Review account usage#

Open Billing Dashboard for the intended account. Inspect usage, subscriptions, and available cost/trend history for the selected period. Compare equivalent intervals before drawing conclusions about a change in cost.

The dashboard reflects the account API’s available information. A missing subscription field is different from a zero charge, and a partial current month should not be compared directly with a completed month. Use the account’s billing records when you need the final invoice.

Separate platform and application health#

Open Cloudflare Status to inspect current service health, incidents, and scheduled maintenance. Enable incident notifications if you want status changes in the IDE. Check which product and time range an incident actually affects.

A healthy platform status does not prove that your own Worker, DNS configuration, or database query is working. Combine platform information with Worker logs and traces when diagnosing a request failure.

Organize CloudBlog entries#

CloudBlog aggregates supported Cloudflare, AWS, and Azure feeds. Filter by provider/topic, open an entry, and bookmark items you want to revisit. Feed entries are external articles, not a statement that every discussed service is managed by this plugin.

A useful investigation sequence is: note the application’s failing request and time, inspect its own logs, check matching platform incidents, then consult relevant release/news entries for context. This keeps an unrelated news item from becoming the assumed cause.

Capture a useful report#

Include the account/profile, affected product, selected period, visible error, and request/deployment identity when available. A screenshot of the relevant panel is useful; credential values are not needed to explain a permissions or rendering problem.