Just built a cost model. The per-GB model gets scary with big, long attacks.

Just finished a cost analysis for a client considering Prolexic. The per-GB scrubbing model is a trap if you face volumetric attacks.

A sustained 50 Gbps attack for a day? That's over 500 TB of traffic to scrub. At their list rates, the bill is astronomical. They're effectively charging you for the attacker's bandwidth. Makes the annual commit models look like the only sane option, but then you're locked in. The pricing heavily incentivizes you to over-provision your commit just to avoid the shock. Feels like you're buying insurance from the arsonist. Anyone else run the numbers and come to the same conclusion? What are you doing to mitigate this?