Summary

Cloudflare will enable budget alerts by default for eligible Pay-as-you-go accounts starting 2026-07-20. If your account has no existing budget alert, Cloudflare will create a $10 account-level alert that becomes active at the start of your next billing cycle. Rollout is done in cohorts over the coming weeks.

Key Points

• Default alert: $10 account-level threshold created for eligible Pay-as-you-go accounts that lack a budget alert.
• Activation timing: the default alert enables at the turn of your next billing cycle and will not retroactively fire for past usage.
• Alert behavior: functions like a user-created alert — an email is sent when cumulative usage-based spend this cycle reaches the threshold.
• Processing cadence: usage is processed once per day (alerts fire the day after the threshold is reached, not in real time).
• Spend considered: only usage-based product charges count; recurring subscription or monthly plan fees (e.g., Workers Paid plan fee) are excluded.
• Control: you can change the threshold, add alerts, or remove the default alert from Manage Account > Billing > Billable Usage or from Notifications settings.
• Exceptions: Enterprise contract accounts are out of scope. If you already set up a budget alert, nothing changes.

Practical actions for engineers

• Verify whether a default alert was created after your next billing cycle begins.
• Update or remove the alert if $10 is not appropriate for your account exposure.
• Integrate billing-monitoring into your existing alerting or cost controls since Cloudflare alerts are informational and do not cap usage.