Michael JohnsonIf you’re building search across a site or data in R2 with Cloudflare AI Search, you should now check two separate settings: when billing begins and how often the index refreshes. On November 2, 2026, Cloudflare announced that billing will begin on December 1 instead of November 1, and that the default sync interval will increase from six to 24 hours. The first change affects the expense calendar; the second changes expectations for data freshness.
What changed and when
The billing deferral runs through December 1, 2026: Cloudflare says AI Search usage will not be billed before that date. The company says prices and included usage allowances remain unchanged. So the news changes when expenses begin, not the announced pricing terms.
Separately, Cloudflare has set 24 hours as the default interval for automatic synchronization. The previous default was six hours. You can change the setting in an instance’s configuration or pass it through the sync_interval field when creating or updating an instance. For external sources, the documentation lists intervals from 15 minutes to 24 hours; the API value is specified in seconds. The syncing documentation also describes starting a task manually or through an automated pipeline.
Why sync frequency matters for search results
AI Search indexes source content so it can find that content in response to a search query. For websites and R2, the service regularly runs sync tasks and processes new, changed, or deleted files. With a 24-hour schedule, a change to the source may have to wait longer for the next run than it would with a six-hour interval.
This matters in scenarios where users expect nearly up-to-date information, such as search across a frequently changing catalog or a database of internal instructions. If content changes infrequently, daily synchronization may suit the workflow. If changes need to appear in search sooner, the team should check the configured schedule and, if necessary, choose a shorter supported interval.
A daily schedule is the default, not a mandatory limit for every instance. You can set a supported interval separately. For changes tied to publishing content or completing a build, Cloudflare also describes triggering synchronization from a content pipeline. The documentation says these tasks can be started no more than once every 30 seconds; the actual time for content to appear also depends on task execution and processing.
How to separate budget from data freshness
A practical review starts with two separate questions. First: when will the service start charging, and which included usage allowances and rates apply? Second: how often does the instance detect changes in its connected source? The answer to one does not replace the answer to the other: the free period through December 1 does not determine the indexing interval, and more frequent synchronization does not itself change the billing start date.
For each instance, it is useful to record the source type, current interval, expected update delay, and synchronization trigger. Then compare that delay with how quickly content becomes outdated in your use case. Daily updates may be acceptable for a document archive or reference site; for a catalog with live changes, consider a more frequent schedule or a trigger after a publishing event. Make this decision based on the pricing documentation and the instance’s actual settings, not on the payment deferral date.
What to check before December 1
Check the sync settings for every active instance: the default change is especially important for those who were counting on the previous six-hour interval. If data needs to update more frequently than once a day, set an appropriate supported interval or plan to trigger synchronization from a content pipeline. At the same time, mark December 1 in your financial planning and check the current AI Search limits and pricing page, where Cloudflare lists the billing start date and included usage.
The takeaway for teams is simple: the budget calendar has shifted by a month, while the default refresh frequency has become four times less frequent. Before launching or continuing to use AI Search, make separate decisions about spending and acceptable index update delays—that combination determines whether the configuration suits your product.
