Argo charging for cached requests

I just read that argo only costs on uncached requests. Yet I was being charged for both cached and uncached requests and even more for some unknown reason.

Below are the screenshots indicating the 24h usage of cached and uncached requests and the other one shows what argo charged me for.

Cached and uncached requests:


1 Like


If you visit and then Argo Smart Routing you will see the pricing and it will look something like this:

Specifically the part that explains how the charging works:

Argo is a usage-based product and costs USD $5.00 per month, plus usage. After exceeding the first gigabyte of traffic between Cloudflare and your visitors, you are charged USD $0.10 per additional gigabyte.

The key part there is traffic between Cloudflare and your visitors - you are charged on that bandwidth.

So is it correct to say that all bandwidth is charged including cached, uncached and others.
Can you verify this?

It is correct, yes.

@simon I’m concerned about how Argo might potentially raise the operational costs of the website in the event of a DDoS attack.

Using Argo seems risky, particularly when considering the possibility of a DDoS attack, which can lead to a sudden surge in bandwidth usage, as I have experienced before. I can provide a screenshot as proof.

Is there any approach or solution that can assist me in this situation?

So, I checked internally as our principle has always been that detected attacks aren’t charged for in Argo:

If you are charged for an unmitigated attack, definitely get in touch and we can take a look.

1 Like