To ensure successful connectivity with Glean, both from your connected apps and for your users, it is essential to allowlist Glean IP ranges through any firewalls and security controls you have in place. Failure to do so may prevent Glean from receiving data from connected data sources and/or hinder users from connecting to Glean.
There are two categories of IP addresses that you must allowlist: the IP addresses for Glean Central and the IP addresses of your specific Glean tenant.
Glean Central
Glean operates a centralized control plane tenant called "Glean Central," which is critical to the service. Glean Central is responsible for:
- Orchestrating all underlying customer environments.
- Pushing service updates to all tenancies.
- Handling tenancy lookup and redirection during user login.
- Aggregating health data and anonymized analytics for each tenancy.
- Managing front-end and routing of OAuth flows from certain apps like Box, Jira, etc., to the corresponding customer tenancy.
Glean Central uses the following static IP addresses:
104.154.230.46/32
35.239.35.180/32
34.120.39.18/32
35.238.31.70/32
34.120.90.191/32
34.120.148.20/32
34.111.103.238/32
34.160.40.155/32
Update History
| 2024-08-19 | Initial post. |
Customer Tenant
Each Glean customer tenancy is deployed in isolation and receives its own "backend" domain (e.g., companyname-be.glean.com). Each tenancy is assigned three (3) public IP addresses used for:
- Inbound webhooks/notifications from connected apps.
- Crawler egress.
- Load balancing for inbound user queries from the Glean app/interface, as well as any requests from the Glean API.
Please contact Glean Support to obtain the IP addresses associated with your specific Glean environment.