GTmetrix: IPs & Locations
Verified GTmetrix IP Addresses. Copy-Paste Firewall-Setups.
Every official GTmetrix monitoring IP: verified in real-time against the canonical source, featuring ready-to-use firewall templates. Stop false downtime alerts caused by blocked checking nodes on your infrastructure.
Made and Hosted in the
European Union
GDPR-Compliant Hosting
in Germany
GEO-Redundant Replica
across the EU
Three-Step Activation & Frictionless Firewall Alignment
Bring your perimeter security rules up to date in three simple steps. Our production-ready configuration templates for common server architectures eliminate fragmented routing filters and costly check flapping.
58 IPv4 addresses from 25 test locations worldwide: one click below copies everything as a plain list or as ready-to-paste UFW, nginx, or Apache config.
Add every address to your allow list: UFW, nginx, Apache, or a Cloudflare/WAF skip rule. Partial lists cause flapping checks and false alerts.
GTmetrix updates its list occasionally. This page was verified on 2026-06-12 against the official source. Re-check after unexplained alerts or automate the sync.
Official GTmetrix Monitoring IPs
GTmetrix publishes every test location with its server IPs on the official locations page.
GTmetrix runs Lighthouse-based performance tests and scheduled monitoring from test servers in 25 locations worldwide. If your WAF, bot protection, or rate limiter challenges those servers, your reports show inflated timings, blocked resources, or the test fails outright.
Whitelist the test server IPs below so performance results reflect what real users experience instead of your firewall.
This list contains 58 IPv4 addresses, verified against the official source on 2026-06-12.
IPv4 addresses 58
- 4.255.141.203
- 4.255.152.17
- 130.131.80.25
- 135.224.6.121
- 172.178.46.205
- 172.178.69.75
- 68.155.155.192
- 68.155.155.195
- 20.175.103.203
- 4.248.66.111
- 20.165.40.104
- 4.150.24.180
- 4.150.58.128
- 4.151.153.232
- 20.66.104.166
- 52.159.252.135
- 4.154.170.206
- 4.155.232.126
- 4.155.4.251
- 4.155.83.118
- 68.211.125.30
- 68.211.125.58
- 4.201.153.91
- 4.201.205.72
- 128.251.154.106
- 98.71.220.188
- 131.189.105.2
- 135.220.45.129
- 172.166.160.11
- 172.166.197.132
- 172.166.212.30
- 172.167.157.85
- 172.167.158.36
- 172.167.37.236
- 158.158.107.119
- 158.158.99.142
- 4.211.187.66
- 4.211.207.165
- 20.91.251.60
- 4.223.126.117
- 74.243.247.23
- 74.243.249.73
- 20.214.16.34
- 20.214.40.188
- 135.13.24.38
- 52.140.18.69
- 20.255.152.94
- 52.175.27.162
- 74.225.139.157
- 74.225.217.56
- 4.193.251.82
- 4.194.210.160
- 20.58.136.237
- 4.196.89.67
- 130.33.49.70
- 130.33.73.187
- 4.221.169.10
- 4.221.208.40
Last verified: 2026-06-12
Official source: https://gtmetrix.com/locations.html
Where GTmetrix Checks From
Official location data from the provider: addresses grouped by check location.
| Location | IP addresses |
|---|---|
| Cheyenne, WY, USA | 4.255.141.203 · 4.255.152.17 |
| Chicago, IL, USA | 130.131.80.25 · 135.224.6.121 |
| Danville, VA, USA | 172.178.46.205 · 172.178.69.75 |
| Mexico City, Mexico | 68.155.155.192 · 68.155.155.195 |
| Quebec City, Canada | 20.175.103.203 · 4.248.66.111 |
| San Antonio, TX, USA | 20.165.40.104 · 4.150.24.180 · 4.150.58.128 · 4.151.153.232 |
| San Francisco, CA, USA | 20.66.104.166 · 52.159.252.135 |
| Seattle, WA, USA | 4.154.170.206 · 4.155.232.126 · 4.155.4.251 · 4.155.83.118 |
| Santiago, Chile | 68.211.125.30 · 68.211.125.58 |
| São Paulo, Brazil | 4.201.153.91 · 4.201.205.72 |
| Amsterdam, Netherlands | 128.251.154.106 · 98.71.220.188 |
| Frankfurt, Germany | 131.189.105.2 · 135.220.45.129 |
| London, UK | 172.166.160.11 · 172.166.197.132 · 172.166.212.30 · 172.167.157.85 · 172.167.158.36 · 172.167.37.236 |
| Madrid, Spain | 158.158.107.119 · 158.158.99.142 |
| Paris, France | 4.211.187.66 · 4.211.207.165 |
| Stockholm, Sweden | 20.91.251.60 · 4.223.126.117 |
| Dubai, UAE | 74.243.247.23 · 74.243.249.73 |
| Busan, South Korea | 20.214.16.34 · 20.214.40.188 |
| Chennai, India | 135.13.24.38 · 52.140.18.69 |
| Hong Kong, China | 20.255.152.94 · 52.175.27.162 |
| Pune, India | 74.225.139.157 · 74.225.217.56 |
| Singapore | 4.193.251.82 · 4.194.210.160 |
| Sydney, Australia | 20.58.136.237 · 4.196.89.67 |
| Tokyo, Japan | 130.33.49.70 · 130.33.73.187 |
| Johannesburg, South Africa | 4.221.169.10 · 4.221.208.40 |
Whitelisting GTmetrix-Monitoring IPs
Pick a format. The block below contains the complete config for every address in the list above. The plain list is also available as a .txt download.
ufw allow from 4.255.141.203 ufw allow from 4.255.152.17 ufw allow from 130.131.80.25 ufw allow from 135.224.6.121 ufw allow from 172.178.46.205 ufw allow from 172.178.69.75 ufw allow from 68.155.155.192 ufw allow from 68.155.155.195 ufw allow from 20.175.103.203 ufw allow from 4.248.66.111 ufw allow from 20.165.40.104 ufw allow from 4.150.24.180 ufw allow from 4.150.58.128 ufw allow from 4.151.153.232 ufw allow from 20.66.104.166 ufw allow from 52.159.252.135 ufw allow from 4.154.170.206 ufw allow from 4.155.232.126 ufw allow from 4.155.4.251 ufw allow from 4.155.83.118 ufw allow from 68.211.125.30 ufw allow from 68.211.125.58 ufw allow from 4.201.153.91 ufw allow from 4.201.205.72 ufw allow from 128.251.154.106 ufw allow from 98.71.220.188 ufw allow from 131.189.105.2 ufw allow from 135.220.45.129 ufw allow from 172.166.160.11 ufw allow from 172.166.197.132 ufw allow from 172.166.212.30 ufw allow from 172.167.157.85 ufw allow from 172.167.158.36 ufw allow from 172.167.37.236 ufw allow from 158.158.107.119 ufw allow from 158.158.99.142 ufw allow from 4.211.187.66 ufw allow from 4.211.207.165 ufw allow from 20.91.251.60 ufw allow from 4.223.126.117 ufw allow from 74.243.247.23 ufw allow from 74.243.249.73 ufw allow from 20.214.16.34 ufw allow from 20.214.40.188 ufw allow from 135.13.24.38 ufw allow from 52.140.18.69 ufw allow from 20.255.152.94 ufw allow from 52.175.27.162 ufw allow from 74.225.139.157 ufw allow from 74.225.217.56 ufw allow from 4.193.251.82 ufw allow from 4.194.210.160 ufw allow from 20.58.136.237 ufw allow from 4.196.89.67 ufw allow from 130.33.49.70 ufw allow from 130.33.73.187 ufw allow from 4.221.169.10 ufw allow from 4.221.208.40
Cloudflare / WAF: create an IP Access Rule (or custom WAF skip rule) with action Allow for the addresses above, so bot fight mode and managed challenges never block probe traffic.
Whitelisting only exempts these addresses from blocking and rate-limiting rules. It grants no access beyond what your site already serves publicly.
Frequently Asked Questions
A common cause is bot protection challenging the test servers: extra JavaScript challenges and delays end up in your measurement. Whitelisting the test IPs removes that distortion.
The official locations page lists IPv4 addresses per location. Check it for current IPv6 specifics.
Occasionally, when locations are added or servers move. The locations page is the canonical source. Re-sync it periodically.
Both: wherever requests can be blocked. If your site sits behind a CDN or WAF (Cloudflare, AWS WAF, Akamai…), add an allow/skip rule there so probes are never challenged; if your origin firewall also filters traffic, whitelist them there too. A single missed layer is enough to cause false alerts.
Most providers expose a machine-readable source (linked above). Fetch it on a schedule, a small cron job that pulls the list and updates your firewall ruleset, instead of hardcoding addresses by hand. This page is re-verified against the official source regularly, but automation on your side is the most reliable option.
No. Allow-listing only exempts known monitoring addresses from blocking and rate-limiting rules. It grants no access beyond what your site already serves publicly, and authentication, authorization, and TLS are unchanged. You are simply telling your firewall "these are not attackers".
A blocklist keeps known-bad addresses out; an allow/whitelist makes sure known-good addresses, here, the monitoring probes, never end up caught in a block or rate-limit rule. The two coexist: you keep blocking attackers while explicitly exempting the probes.
The IP addresses on this page belong to GTmetrix and are published by GTmetrix for whitelisting purposes. List verified on 2026-06-12 against the official source. Always cross-check with the official documentation before locking down production firewalls. All product names and trademarks are the property of their respective owners; Uptimeify is not affiliated with GTmetrix. Uptimeify's own worker IPs are published at /ips.txt; a feature comparison is on our comparison page.
Monitoring Without IP Guesswork.
Protect your clients' digital assets and lock down your webserver routing. Leverage our verified network catalogs for clean whitelist setups, or migrate directly to the rock-solid, EU-only architecture of Uptimeify.