---
title: "Comment by IP99 on \"I burned a 2 GB residential proxy in a weekend — the real numbers\" | Hashnode"
description: "The bandwidth burn rate is painfully familiar. From the defender side, residential exits are exactly why network-type blocklists fail: the address looks like ho"
url: "https://hashnode.com/posts/i-burned-a-2-gb-residential-proxy-in-a-weekend-the-real-numbers/6ab53d6e95929c122b9f2065/comment/6acf4ff68e1bc8c6f39e7c32"
---

[Discussion](https://hashnode.com/posts/i-burned-a-2-gb-residential-proxy-in-a-weekend-the-real-numbers/6ab53d6e95929c122b9f2065)

Comment [I burned a 2 GB residential proxy in a weekend — the real numbers](https://hashnode.com/posts/i-burned-a-2-gb-residential-proxy-in-a-weekend-the-real-numbers/6ab53d6e95929c122b9f2065)

[IP99](https://hashnode.com/@ip99)

[Oct 14](https://hashnode.com/posts/i-burned-a-2-gb-residential-proxy-in-a-weekend-the-real-numbers/6ab53d6e95929c122b9f2065/comment/6acf4ff68e1bc8c6f39e7c32)

The bandwidth burn rate is painfully familiar. From the defender side, residential exits are exactly why network-type blocklists fail: the address looks like home broadband until you check proxy-class evidence.

IP99 / ThreatHunter keeps a live risk feed on those exits (proxy, VPN, dial-up pools) with scores that expire when the evidence goes stale. Handy when you’re validating whether a “clean” residential IP is actually a recycled proxy exit.