Argo billing
1. Is Argo enabled per domain or per account? When I tried to test it with one of my domains, the system asked me if I would enable it for my account, and I don’t want to enable it for every domain on my account.
2. How do you determine the size? Would it be the total request size as observed by the “total data served” on my panel? Trying to determine if I could afford this since most of my sites are image heavy, and I mainly want to use Argo for the HTML.
Don’t know which tag to use so I picked DNS…
4 Replies
It's per domain, that wording is weird though
2. It's upload + download bytes from cf -> user: https://community.cloudflare.com/t/we-are-being-charged-more-on-argo-then-usage/689733/6?u=chaika
Zone Analytics only shows downloads
Thanks!
When calculating uploads, and if the image assets are already cached (eg a month), then accessed 30 times, then the result would be:
image size x (30 + 1)
correct? Mostly making sure that I understand this correctly.
Roughly, with a few notes:
1. Assuming that the upload is coming through that zone, which wouldn't be the case if using r2 presigned URLs or CF Images
2. You're excluding compression which could and would happen automagically reducing bandwidth between cf -> user on downloads
if the image assets are already cached (eg a month),The billing of Argo has nothing to do with cache tho
The assumption I made about cache is that if it’s already cached on CF, then they won’t need to be uploaded to CF again — thus saving trip from origin to CF.
I didn’t think that R2 to CF would also be considered as part of the trip though. Thanks!