Cloudflare R2 adds location-level bandwidth reporting
The October 9 R2 update helps publishers investigate file delivery. Keep network location, visitor geography and conversion results separate.
On October 9, 2026, Cloudflare announced R2 bandwidth reporting by serving location. It matters to publishers already using R2 for their own files. Service availability still determines geographic applicability; this is not a country-expansion announcement.
The bandwidth dataset excludes transfers below 100 KiB; it is not a complete file ledger.
What changed
The interface allows bucket selection and separates downloads from uploads. It displays five locations by default and allows up to six selections. These are infrastructure transfer measurements.
Put the report to work
The following workflow is AffiliateCore editorial advice, not a claim about results achieved with Cloudflare.
- Choose one bucket with a known collection of files and record the time window. Keep an image library separate from another project's backups.
- Review reads and writes separately. Compare a spike following a content update with the time new files were uploaded.
- To investigate oversized images, compare individual object sizes before and after the change. Retain the changed-file list and previous version.
- Compare the observation with your own delivery errors and page-speed measurements. A bytes chart alone cannot demonstrate a useful optimization.
Illustrative workflow: transfer increase → inspect file composition → check page loading → decide on one change. This is not a customer-site experiment.
What it cannot establish
Do not infer a visitor's country solely from the serving location. More transferred data does not establish more unique visitors, leads or confirmed conversions. Those conclusions require separate, consistently defined measurements.
The first review should produce a record of bucket, period, transfer direction, changed files, observation and next check. If the explanation remains unclear, retain a hypothesis rather than declaring a cause. Do not change offer geography or routing based on a single infrastructure chart.
Next: mobile performance priorities. R2 is an external service, not a claimed built-in AffiliateCore feature.