-
Notifications
You must be signed in to change notification settings - Fork 15.9k
[Billing] Add changelog for default-on Budget alerts #31467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: production
Are you sure you want to change the base?
Changes from 4 commits
a5face1
9167b5a
06b2f80
8893e14
6c45021
287f905
a27a38f
10cc388
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| --- | ||
| title: Budget alerts now on by default for Pay-as-you-go accounts | ||
| description: Eligible Pay-as-you-go accounts now receive an automatic $10 budget alert at the start of each new billing cycle. You can edit the threshold or remove the alert at any time. | ||
| products: | ||
| - billing | ||
| date: 2026-06-15 | ||
| --- | ||
|
|
||
| We are turning on Budget alerts by default for eligible Pay-as-you-go accounts. If your account does not already have a budget alert, Cloudflare will create one for you with a $10 account-level threshold. Your default alert will enable at the turn of your next billing cycle, so it will not fire based on usage you have already incurred. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Why this caveat?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Think I answered this in Gchat somewhere, but confirming. We don't want mid cycle alerts firing to create noise upon creation due mostly due to sensitivity around escalations and tickets. Just being safe. |
||
|
|
||
| The default alert behaves exactly like an alert you would create yourself. When your cumulative usage-based spend this cycle reaches the threshold, you receive an email notification. The alert is informational only. It does not cap your usage or impact your account in any way. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Who on the account gets an email notification?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this goes to the primary email on file; same as where the invoice is delivered
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should mention alerting delay so users aren't confused why their alert has not triggered?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. updated. thank you |
||
|
|
||
| Budget alerts only consider spend on usage-based products. Recurring subscription fees, such as the Workers Paid plan fee or other monthly plan charges, are not included in the threshold calculation. | ||
|
|
||
| You can change the threshold, add additional alerts, or remove the default alert entirely from **Manage Account** > **Billing** > **Billable Usage**, or from your Notifications settings. If you already configured your own budget alert, nothing changes. | ||
|
|
||
| Default alerts are available for Pay-as-you-go accounts with active usage-based products. Enterprise contract accounts are not in scope. | ||
|
|
||
| For more information, refer to the [Budget alerts documentation](/billing/manage/budget-alerts/). | ||
Uh oh!
There was an error while loading. Please reload this page.