All Gearset requests, regardless of which Gearset instance you are using, originate from one of these static IP addresses in the table below.
(If you are unsure which Gearset instance you are on, you can check here.)
Depending on your corporate firewall settings, you may need to add logins from these IPs to the allowlist for Gearset to be able to connect to your on-premise version control system or to orgs with IP access restrictions enabled.
You should allow TCP port 443 for HTTPS (or TCP port 22 for SSH).
As you can see 4 of the IPs listed are common across the instances, if you would like to learn more about it, this article provides further information.