<story><title>Cloudflare&apos;s new Argo feature billing surprise</title><text>A heads up for any other Cloudflare customers that have enabled Argo. This feature is supposed to improve performance due to better routing but what is not mentioned is that any abuse traffic, even explicitly blocked traffic is still counted against the $0.10 &amp;#x2F; GB.&lt;p&gt;I had an attack come in a few days ago generating false traffic and blocked it via Cloudflare&amp;#x27;s IP firewall. All traffic, including blocked, still counts towards billable per gigabyte bandwidth as confirmed by their support staff. They may sometime in the future separate the counts but for now the support recommendation is to disable Argo.</text></story><parent_chain></parent_chain><comment><author>jgrahamc</author><text>Cloudflare CTO here. I&amp;#x27;ll look into this. Doesn&amp;#x27;t make sense we&amp;#x27;d charge you for traffic we filtered out.</text></comment>
<story><title>Cloudflare&apos;s new Argo feature billing surprise</title><text>A heads up for any other Cloudflare customers that have enabled Argo. This feature is supposed to improve performance due to better routing but what is not mentioned is that any abuse traffic, even explicitly blocked traffic is still counted against the $0.10 &amp;#x2F; GB.&lt;p&gt;I had an attack come in a few days ago generating false traffic and blocked it via Cloudflare&amp;#x27;s IP firewall. All traffic, including blocked, still counts towards billable per gigabyte bandwidth as confirmed by their support staff. They may sometime in the future separate the counts but for now the support recommendation is to disable Argo.</text></story><parent_chain></parent_chain><comment><author>asadlionpk</author><text>I have been thinking of enabling this feature. Aside from this issue, does it make visible difference in terms of performance?</text></comment>