What IP Addresses does SiteDash use?
SiteDash connects with your site through HTTP requests. These requests may come from a variety of servers that we refer to as workers. In some cases you may find a firewall, mod_security, or other security implementation on your server to block these requests.
If possible, whitelisting the "SiteDash.app" user agent or the assets/components/sitedashclient/ path would be preferable over whitelisting IPs. We occasionally add or replace servers, so if you have a firewall that requires the whitelisting, please check back here every couple of months or so for updates.
The following IPs are used for general tasks and monitoring:
| Internal server name | IPv4 | IPv6 |
| w2 | 167.99.215.0 | 2a03:b0c0:2:d0::11d:5001 |
| w3 | 142.93.143.118 | 2a03:b0c0:2:f0::31:7001 |
| w4 (lighthouse) | 104.248.195.103 | 2a03:b0c0:2:d0::13:4001 |
| w5 (monitoring) | 134.209.83.170 | 2a03:b0c0:2:f0::cc:9001 |
| web1 (rarely) | 178.62.250.146 | 2a03:b0c0:2:d0::cd:7001 |
The following IPs are used for extended uptime monitoring:
| Cluster | Location | IPv4 addresses | IPv6 addresses |
| EU-AMS | Amsterdam, The Netherlands | 159.65.197.158 | 2a03:b0c0:2:d0::1123:a001 |
| NA-NYC | New York, United States | 164.90.143.226 |
2604:a880:800:10::827:8001 |
Each cluster may be assigned additional servers at any time.
If you have a significant number of sites (50-100) that you would like to use Extended Monitoring on, but would like a more local cluster than what we currently offer, please get in touch. We can run our monitoring clusters on a variety of cloud providers with locations all around the world and scale it based on demand.