Glean IP ranges
Allowlist the required IP ranges through your firewalls and security controls to connect to Glean services. These ranges support connections from Glean to connected connectors and from users to Glean services.
There are two categories of IP addresses to allowlist: Glean Central addresses and the addresses assigned to your Glean tenant.
Glean Central
Glean Central serves as the centralized control plane tenant for the service. This infrastructure component is responsible for:
- Orchestrating customer environments
- Pushing service updates to all tenancies
- Handling tenancy lookup and redirection during user sign-in
- Aggregating health data and anonymized analytics for each tenancy
- Managing the front end and routing OAuth flows from apps such as Box and Jira to the corresponding customer tenancy
Glean Central IP addresses
The following static IP addresses are used by Glean Central and should be allowlisted:
104.154.230.46/32
35.239.35.180/32
34.120.39.18/32
34.144.241.72/32
34.120.90.191/32
34.120.148.20/32
34.111.103.238/32
34.160.40.155/32
These CIDRs must be permitted for AWS deployments:
98.89.71.36/32
Last updated: August 13, 2026
Customer tenant configuration
Each Glean customer deployment operates in isolation with its own dedicated backend domain, such as companyname-be.glean.com. Your tenancy is assigned three public IP addresses for these purposes:
- Inbound webhooks: Handles notifications and webhooks from connected applications
- Crawler egress: Manages outbound connections for data crawling operations
- Load balancing: Handles inbound user queries from the Glean application interface and API requests
To obtain the specific IP addresses associated with your Glean environment, contact Glean Support.
See also
- Monitoring probe for proxy and connector checks
- Glean Web Application Firewall on AWS for AWS web application firewall controls