My IP Range Calculator
My IP Range Calculator
Most home and office internet connections use a "dynamic" IP that changes periodically (when your router restarts, or your ISP reassigns addresses) - so a Google Analytics 4 internal traffic filter set to your exact IP address will silently stop working the next time it changes. Using a CIDR range instead (like /24, your ISP's likely allocated block) is far more stable, since your IP almost always changes only within that same block.
- Auto-detected, no typing needed: this reads the actual public IP your connection is using right now, from the request that loaded this page - the same address GA4's collection endpoint would see.
- Default /24 range: a /24 covers 256 addresses and is the most common ISP allocation size to test against for home/office connections - adjust the prefix length if you know your provider uses something different.
- Behind a VPN or proxy? This shows the IP your traffic currently exits through, not your device's local network interfaces - if you use a VPN for work, run this while connected to get the range GA4 will actually see.
How do I use this in GA4 internal traffic filtering?
In GA4, go to Admin → Data Streams → your stream → Configure tag settings → Show all → Define internal traffic, create a rule, and set the IP address matching condition to "IP address ranges (CIDR notation)" with the range shown above (e.g. 78.84.170.0/24). Then create a matching data filter under Admin → Data Filters to actually exclude that traffic.
Why use a range instead of my exact IP address?
A single exact-IP filter breaks the moment your ISP assigns you a new dynamic IP, which can happen as often as every router restart. A CIDR range covers the whole block your ISP is likely to reassign addresses from, so the filter keeps working through ordinary IP changes.
My IP Range Calculator
Most home and office internet connections use a "dynamic" IP that changes periodically (when your router restarts, or your ISP reassigns addresses) - so a Google Analytics 4 internal traffic filter set to your exact IP address will silently stop working the next time it changes. Using a CIDR range instead (like /24, your ISP's likely allocated block) is far more stable, since your IP almost always changes only within that same block.
- Auto-detected, no typing needed: this reads the actual public IP your connection is using right now, from the request that loaded this page - the same address GA4's collection endpoint would see.
- Default /24 range: a /24 covers 256 addresses and is the most common ISP allocation size to test against for home/office connections - adjust the prefix length if you know your provider uses something different.
- Behind a VPN or proxy? This shows the IP your traffic currently exits through, not your device's local network interfaces - if you use a VPN for work, run this while connected to get the range GA4 will actually see.
How do I use this in GA4 internal traffic filtering?
In GA4, go to Admin → Data Streams → your stream → Configure tag settings → Show all → Define internal traffic, create a rule, and set the IP address matching condition to "IP address ranges (CIDR notation)" with the range shown above (e.g. 78.84.170.0/24). Then create a matching data filter under Admin → Data Filters to actually exclude that traffic.
Why use a range instead of my exact IP address?
A single exact-IP filter breaks the moment your ISP assigns you a new dynamic IP, which can happen as often as every router restart. A CIDR range covers the whole block your ISP is likely to reassign addresses from, so the filter keeps working through ordinary IP changes.