In some specialised environments where network connections are tightly controlled, you may need to make exceptions for 247connect’s traffic within your network settings, firewall and/or antivirus solutions to enable all of 247connect’s functionality to work as expected.
In most cases, you can add a wildcard approved list of *.247connect.cloud (regardless of what region your organisation is part of). If your solution doesn’t support using wildcards, you need to specify specific domain names.
Below is a list of servers for each region, along with any protocols and ports used by 247connect to communicate with the server:
Global FQDNs
Web portal
- portal.247connect.cloud – HTTPS 443
On-demand link
- 247connect.link – HTTPS 443
Authentication
- auth.247connect.cloud – HTTPS 443
Gateways
- gateway01-uksouth.247connect.cloud – HTTPS 443
- gateway01-gwc.247connect.cloud – HTTPS 443
- gateway01-eastus.247connect.cloud – HTTPS 443
- gateway01-westus.247connect.cloud – HTTPS 443
Gateway APIs
- gatewayapi.247connect.cloud – HTTPS 443
APIs
- api.247connect.cloud – HTTPS 443
- controlapi.247connect.cloud – HTTPS 443
- agentapi.247connect.cloud – HTTPS 443
Data residency specific FQDNs
United Kingdom (UK South) Region
- auth-uksouth.247connect.cloud – HTTPS 443
- gatewayapi-uksouth.247connect.cloud – HTTPS 443
- api-uksouth.247connect.cloud – HTTPS 443
- controlapi-uksouth.247connect.cloud – HTTPS 443
- agentapi-uksouth.247connect.cloud – HTTPS 443
EU/EEA (Germany West Central) Region
- auth-germanywestcentral.247connect.cloud – HTTPS 443
- gatewayapi-germanywestcentral.247connect.cloud – HTTPS 443
- api-germanywestcentral.247connect.cloud – HTTPS 443
- controlapi-germanywestcentral.247connect.cloud – HTTPS 443
- agentapi-germanywestcentral.247connect.cloud – HTTPS 443
United States (US East) Region
- auth-eastus.247connect.cloud – HTTPS 443
- gatewayapi-eastus.247connect.cloud – HTTPS 443
- api-eastus.247connect.cloud – HTTPS 443
- controlapi-eastus.247connect.cloud – HTTPS 443
- agentapi-eastus.247connect.cloud – HTTPS 443