Would be nice if there could be a way to break the list of IP that customers need to whitelist into groups.. So instead of just a huge list like we currently have with site24x7.enduserexperience.com there could be something like:
- uk.site24x7.enduserexperience.com
- au.site24x7.enduserexperience.com
- us-east.site24x7.enduserexperience.com
- us-west.site24x7.enduserexperience.com
- us-south.site24x7.enduserexperience.com
- us-mid.site24x7.enduserexperience.com
Or you can get granular with the US since there are so many groups there, you could break that down by state, for example:
- atlanta-us.site24x7.enduserexperience.com
- california-us.site24x7.enduserexperience.com
- seatle-us.site24x7.enduserexperience.com
- losangeles-us.site24x7.enduserexperience.com
We currently block connections from certain regions and just doing all IPs goes against our best practices. Doing the grouping like above would allow customers to whitelist only the groups they care about and not have to worry about manually updating IPs that match their locations every time that list of IPs change.
Any updates on this?
Whitelisting is proving to be a pain now as we have to keep manually changing our entires each time a change is made for the locations we need to monitor. We have had false alerts many times and it's starting to impact our trust with Site24x7 each time.
Dear Framirez,
First off our apologies for not letting you know that we have implemented this in our end.
The format we have supported is: city-countrycode.enduserexp.com (eg: dallas-us.enduserexp.com). The full list is mentioned in this KBase article.
-Jasper
Product Manager, Site24x7
Hi Jasper,
Sorry for not seeing this earlier. If I add chicago-us.enduserexp.com to our list, will that always show the most recent listing?
I just ran it using dig and got the following:
chicago-us.enduserexp.com. 600 IN A 209.50.53.228
chicago-us.enduserexp.com. 600 IN A 45.135.150.190
chicago-us.enduserexp.com. 600 IN A 209.50.49.76
chicago-us.enduserexp.com. 600 IN A 209.50.50.39
chicago-us.enduserexp.com. 600 IN A 103.214.111.218
chicago-us.enduserexp.com. 600 IN A 108.61.203.16
but on the actual www.site24x7.com/multi-location-web-site-monitoring.html, it looks to be missing the 108.61.203.16 address.
Chicago (Illinois), US
209.50.53.228
209.50.49.76
209.50.50.39
103.214.111.218
45.135.150.190
Was that a typo error or should we not reply on the web page anymore and use the new location domain endpoints instead?