Explo supports multiple multi-tenant, shared connectivity regions for connecting to customer data sources. Selecting a region that is closest in global proximity to your data sources can result in lower query and connection latency and improve your Explo integration performance.

Explo additionally supports separate, isolated connectivity regions for enterprise customers who require them. Contact your Explo Customer Team to discuss your needs.

Enabling access to a connectivity region

Typically you will need to ensure your infrastructure is allowed to receive traffic from the Explo connectivity region you are using. To do so you may need to allowlist traffic from the Explo connectivity region in your infrastructure.

Default connectivity region access

Explo supports multiple connectivity regions, and unless you are informed otherwise by your Explo Customer Team, as a minimum, you may need to allowlist the IPV4 addresses for our legacy US-East-1 and Data Orchestrator US-East-1 regions:

Available Shared Connectivity Regions

Default US-East-1

By default all data source connectivity, queries, and traffic are sourced from our legacy US-East-1 region. Unless your Explo Customer Team informs you otherwise, your connectivity traffic will be sourced from this region.

Explo is actively migrating customers away from this legacy infrastructure. Please also see notes and IP egress information below for the US-East-1 Orchestrator region below where most customers will be migrated to.

Egress IPs

Data Orchestrator US-East-1 (Beta)

Customers are being actively migrated to this new infrastructure which will be the default shortly.

Egress IPs

Future Shared Data Orchestrator Regions

Please reach out to your Explo Customer Team to discuss new region needs.