--- title: "Tulip Cloud deployment networking requirements" slug: "tulip-cloud-deployment-networking-requirements" tags: ["Network", "Requirements", "Tulip Cloud", "Deployment"] status: "update" updated: 2026-10-28T18:22:54Z published: 2026-10-28T18:22:54Z canonical: "support.tulip.co/tulip-cloud-deployment-networking-requirements" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.tulip.co/llms.txt > Use this file to discover all available pages before exploring further. # Tulip Cloud deployment networking requirements ## Overview Tulip is designed to be a versatile tool, but a high-quality network connection is required to reach it reliably. This article lists the specific domains, IP address ranges, and ports to allowlist for Tulip Cloud — covering the Tulip platform, Admin interface, Connector Hosts, Edge Devices, and Tulip Player. For network stability requirements, data-integrity risk, and resilient app design guidance, see [**Network Stability and Data Integrity Requirements for Tulip Cloud Deployments**](/r230/docs/network-stability-and-data-integrity-requirements-for-tulip-cloud-deployments). Also see: [Network Troubleshooting Guide](https://support.tulip.co/docs/network-troubleshooting-guide) ## Who is this article for? This article is most useful for IT and network teams configuring firewall, proxy, and connectivity settings for a Tulip Cloud deployment. Use the links on the right to navigate to relevant sections. ## Allowlist The section below lists all connections Tulip requires to operate as a platform, separated by Tulip component. This list represents a complete list of addresses owned by Tulip. Users can identify the garden identifier where their Tulip Instance is hosted within the Account Settings menu. | **Garden Identifier** | **Inbound to Tulip Cloud Services (Outbound from Customer Network to Tulip Cloud Services)** | **Outbound from Tulip (Inbound from Tulip Cloud Services to Customer Network)** | **Asset Storage** | | --- | --- | --- | --- | | `eu-32*` | - 18.196.208.150 - 52.29.186.76 - 3.65.140.161 - 3.68.164.149 - 3.69.40.142 - 3.78.33.159 | - 18.157.121.27 - 3.123.244.32 - 52.59.20.237 - 3.78.105.122 - 18.193.245.36 - 3.122.220.199 | - https://s3.eu-central-1.amazonaws.com/co.tulip.factory/ | | `eu-70*` | - 4.175.210.240 - 4.175.210.241 - 4.175.210.242 - 4.175.210.243 | - 20.71.18.62 - 51.124.87.41 | - https://dmgtulip.blob.core.windows.net/ | | `apac-94*` | - 20.27.132.100 - 20.27.132.101 - 20.27.132.102 - 20.27.132.103 | - 20.78.30.60 - 20.48.9.84 | - https://dmgjapantulip.blob.core.windows.net/ | | `us-11*` | - 44.227.129.199 - 44.238.198.162 - 44.241.118.68 - 44.231.104.41 - 52.35.58.248 - 52.36.233.68 | - 34.212.49.37 - 52.35.248.97 - 52.10.204.120 - 34.213.88.194 - 52.25.126.217 - 44.240.150.101 | - https://s3.us-west-2.amazonaws.com/co.tulip.tulip-aws-us-west-2-nonprod-11.factory/ | | `us-14*` | - 20.84.217.148 - 20.84.217.149 - 20.84.217.150 - 20.84.217.151 | - 20.84.216.50 | - https://garden14factory.blob.core.windows.net/ | | `us-15*` | - 3.208.72.216 - 3.208.72.217 - 3.208.72.218 - 3.208.72.232 - 3.208.72.233 - 3.208.72.234 | - 3.208.72.210 - 3.208.72.211 - 3.208.72.212 - 3.208.72.229 - 3.208.72.230 - 3.208.72.231 | - https://s3.us-east-1.amazonaws.com/co.tulip.factory/ | | `apac-19*` | - 20.210.51.28 - 20.210.51.29 - 20.210.51.30 - 20.210.51.31 | - 20.210.45.100 | - https://garden19factory.blob.core.windows.net/ | | `cn-20*` | - 159.27.126.40 - 159.27.126.41 - 159.27.126.42 - 159.27.126.43 | - 159.27.127.10 | - https://garden20factory.blob.core.chinacloudapi.cn/ | | `cn-21*` | - 71.132.38.120 - 52.80.236.54 - 71.131.201.160 - 52.81.123.14 - 54.223.195.74 - 54.223.59.65 | - 71.131.201.138 - 71.132.24.122 - 71.132.7.44 - 54.223.241.238 - 54.223.51.22 - 140.179.71.41 | - https://s3.cn-north-1.amazonaws.com.cn/co.tulip.tulip-aws-cn-north-1-prod-21.factory/ | | `usgov-22*` | - 3.30.98.35 - 3.30.98.36 - 3.30.98.37 - 3.30.98.41 - 3.30.98.42 - 3.30.98.43 | - 3.30.98.32 - 3.30.98.33 - 3.30.98.34 - 3.30.98.38 - 3.30.98.39 - 3.30.98.40 | - https://s3.us-gov-west-1.amazonaws.com/co.tulip.factory/ | | `apac-25*` | - 13.214.78.164 - 13.250.183.11 - 52.77.113.195 - 18.139.21.26 - 18.143.235.80 - 13.251.239.252 | - 52.74.23.60 - 54.251.114.217 - 18.141.118.107 - 18.136.228.199 - 52.220.60.219 - 122.248.216.79 | - https://s3.ap-southeast-1.amazonaws.com/co.tulip.tulip-aws-ap-southeast-1-eksapac-25.factory/ | | `eu-27*` | - 51.103.12.96 - 51.103.12.97 - 51.103.12.98 - 51.103.12.99 | - 20.74.20.137 | - https://garden27factory.blob.core.windows.net/ | | `us-28*` | - 4.156.65.240 - 4.156.65.241 - 4.156.65.242 - 4.156.65.243 | - 4.156.123.70 | - https://garden28factory.blob.core.windows.net/ | | `apac-30*` | - 52.193.203.7 - 3.114.39.205 - 54.238.210.93 - 54.168.171.117 - 13.115.103.18 - 52.192.225.86 | - 52.69.36.14 - 18.182.234.190 - 57.181.129.61 - 52.193.201.211 - 3.113.145.191 - 35.79.129.101 | - https://s3.ap-northeast-1.amazonaws.com/co.tulip.tulip-aws-ap-northeast-1-prod-30.factory/ | | `us-33*` | - 3.143.190.234 - 18.189.54.45 - 3.150.60.241 - 3.149.138.1 - 3.141.227.62 - 3.20.218.71 | - 18.225.12.77 - 18.189.216.223 - 3.19.226.227 - 18.189.239.168 - 3.150.156.147 - 13.58.6.116 | - https://s3.us-east-2.amazonaws.com/co.tulip.tulip-aws-us-east-2-prod-33.factory/ | | `us-34*` | - 18.224.75.4 - 3.128.141.5 - 3.129.164.217 - 3.149.124.146 - 3.17.32.22 - 3.23.24.226 | - 3.13.128.10 - 3.147.198.105 - 3.147.35.226 - 3.151.20.57 - 3.151.252.182 - 3.20.93.69 | - https://s3.us-east-2.amazonaws.com/co.tulip.tulip-aws-us-east-2-lilly-34.factory/ | | `apac-35*` | - 52.199.153.102 - 52.199.10.209 - 35.73.173.217 - 52.193.111.59 - 57.182.14.240 - 54.248.198.111 | - 52.196.21.255 - 3.114.176.16 - 35.75.95.95 - 3.113.115.0 - 35.79.74.248 - 13.192.248.106 | - https://s3.ap-northeast-1.amazonaws.com/ | ## Admin interface (Web Browser) To use Tulip's web interface, we require the following: ### **Requirements** Outgoing access to Factory: - https://your-account.tulip.co/ **OR** - https://your-account.dmgmori-tulip.com/ **OR** - https://your-account.tulip-serendie.com/ Outgoing access to Custom Widgets: - *.tulip-custom-widgets.com **OR** - *.dmgmori-tulip-custom-widgets.com Outgoing access to content delivery network (CDN): - [https://s3.amazonaws.com/co.tulip.cdn/](https://s3.amazonaws.com/co.tulip.cdn/) Outgoing access for live chat support: - [https://api-iam.intercom.io/](https://api-iam.intercom.io/) - [https://nexus-websocket-a.intercom.io/](https://nexus-websocket-a.intercom.io/) - *.zopim.com (port 80 and 443) - If wildcards are not allowed, please provide access for the following subdomains: - chat-api.zopim.com - ccapi-larboard.zopim.com - chat-polaris-api.zopim.com - chat-polaris-larboard.zopim.com - widget-mediator.zopimdashboard-mediator.zopim.com - chat-polaris.zopim.com Outgoing access for onboarding interactions: - [https://api.appcues.net/](https://api.appcues.net/) ## Tulip Player To download, use, and update the Tulip Player, we require the following: ### **Requirements** Outgoing access to Factory: - https://your-account.tulip.co/ **OR** - https://your-account.dmgmori-tulip.com/ **OR** - https://your-account.tulip-serendie.com/ Outgoing access to Custom Widgets: - *.tulip-custom-widgets.com **OR** - *.dmgmori-tulip-custom-widgets.com Outgoing access to content delivery network (CDN): - [https://s3.amazonaws.com/co.tulip.cdn/](https://s3.amazonaws.com/co.tulip.cdn/) Outgoing access for Player updates: - [https://download.tulip.co](https://download.tulip.co/)/ - [https://s3.amazonaws.com/download.tulip.co/](https://s3.amazonaws.com/download.tulip.co/) For Players used in China For customers using Tulip Player within China, we recommend following the [Tulip Player Enterprise Deployments](https://support.tulip.co/docs/tulip-player-enterprise-deployments#customers-based-in-china) and granting access to the relevant download URLs. ## Tulip Edge Devices To use and update Tulip's hardware, we require the following: **Requirements** Outgoing access to Factory: - https://your-account.tulip.co/ **OR** - https://your-account.dmgmori-tulip.com/ **OR** - https://your-account.tulip-serendie.com/ Outgoing access for Edge Device updates: - [https://firmware.tulip.co](https://firmware.tulip.co) - [https://s3.amazonaws.com/co.tulip.mender-artifact-storage](https://s3.amazonaws.com/co.tulip.mender-artifact-storage) Outgoing access for date time synchronization: - ntp://[0-3].north-america.pool.ntp.org ## Tulip Cloud Connector Host To use the Tulip Cloud Connector Host to connect to a database, API, or OPC UA server, we require the following: #### **Requirements** Incoming access to Factory: - https://your-account.tulip.co/ **OR** - https://your-account.dmgmori-tulip.com/ **OR** - https://your-account.tulip-serendie.com/ ## Tulip On Premise Connector Host To use the self-hosted Docker Tulip Connector Host to connect to a database, API, or OPC UA server, we require the following: ### **Requirements** Outgoing access to Factory: - https://your-account.tulip.co/ **OR** - https://your-account.dmgmori-tulip.com/ **OR** - https://your-account.tulip-serendie.com/ Outgoing access for updates: - [https://bckca2dh98.execute-api.us-east-1.amazonaws.com](https://bckca2dh98.execute-api.us-east-1.amazonaws.com) Outgoing access for connections: - All third-party services to be connected to Tulip. ## Revision history (since February 2025) | Area of Revision | Date of Revision | Revision Summary | | --- | --- | --- | | [IP Allowlist](/r230/docs/tulip-cloud-deployment-networking-requirements#allowlist) | 10/28/2026 | Improved garden details of identifier `apac-35*` | | Network stability and data integrity requirements for Tulip cloud deployments | 07/29/2026 | Moved advanced topics to a [separate article](/r230/docs/network-stability-and-data-integrity-requirements-for-tulip-cloud-deployments). | | [IP Allowlist](/r230/docs/tulip-cloud-deployment-networking-requirements#allowlist) | 07/29/2026 | Added IP allowlist for garden with identifier `apac-35*` | | [Tulip Player](/r230/docs/tulip-cloud-deployment-networking-requirements##tulip-player) | 02/13/2026 | Added reference for Tulip player usage from within China | | [IP Allowlist](/r230/docs/tulip-cloud-deployment-networking-requirements#allowlist) | 01/14/2026 | Added IP allowlist for garden with identifier `us-34*` | | - [Executive summary](/r230/docs/tulip-cloud-deployment-networking-requirements#executive-summary) - [Instability risks and data integrity](/r230/docs/tulip-cloud-deployment-networking-requirements#instability-risks-and-data-integrity) - [How network issues cause data loss in the Trigger Queue](/r230/docs/tulip-cloud-deployment-networking-requirements#how-network-issues-cause-data-loss-in-the-trigger-queue) - [Risk factor for data loss](/r230/docs/tulip-cloud-deployment-networking-requirements#risk-factors-for-data-loss) - [ALCOA compliance for life sciences](/r230/docs/tulip-cloud-deployment-networking-requirements#alcoa-compliance-for-life-sciences) - [Quantifiable network requirements](/r230/docs/tulip-cloud-deployment-networking-requirements#quantifiable-network-requirements) - [Physical infrastructure recommendations](/r230/docs/tulip-cloud-deployment-networking-requirements#physical-infrastructure-recommendations) - [Logical and security infrastructure (proxies, firewalls, and DPI)](/r230/docs/tulip-cloud-deployment-networking-requirements#logical-and-security-infrastructure-proxies-firewalls-and-dpi) - [Resilient app architecture](/r230/docs/tulip-cloud-deployment-networking-requirements#resilient-app-architecture) - [Technical configuration and troubleshooting](/r230/docs/tulip-cloud-deployment-networking-requirements#technical-configuration-and-troubleshooting) | 11/18/2025 | New sections and information | | [Admin Interface (Web Browser)](/r230/docs/tulip-cloud-deployment-networking-requirements#admin-interface-web-browser) & [IP Allowlist](/r230/docs/tulip-cloud-deployment-networking-requirements#allowlist) | 10/23/2025 | Updated IP allowlist based on garden identifiers & removed outdated CSV import requirements | | [Allowlist](/r230/docs/tulip-cloud-deployment-networking-requirements#allowlist) / Region: us | 9/29/2025 | Added "20.84.216.50" to Connector Host addresses in us region | | [Allowlist](/r230/docs/tulip-cloud-deployment-networking-requirements#allowlist) / Region: us | 9/13/2025 | One Connector Host address updated from ‘20.84.217.148/31’ To ‘20.84.217.148/30’ | | [Admin Interface (Web Browser)](/r230/docs/tulip-cloud-deployment-networking-requirements#admin-interface-web-browser) & [Tulip Player](/r230/docs/tulip-cloud-deployment-networking-requirements#tulip-player) | 4/17/2025 | Improved highlighting of requirement for Custom Widgets | | [Allowlist](/r230/docs/tulip-cloud-deployment-networking-requirements#allowlist) / Region: apac | 2/27/2025 | - Instance & Connector Host: Additional I.P. addresses. - Additional URL in Asset Storage | | [Admin Interface (Web Browser)](/r230/docs/tulip-cloud-deployment-networking-requirements#admin-interface-web-browser) & [Tulip Player](/r230/docs/tulip-cloud-deployment-networking-requirements#tulip-player) | 2/12/2025 | New requirement for Custom Widgets | --- Did you find what you were looking for? You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have solved a similar topic! **Tulip Player** **Tulip Player** is the Windows/Mac executable program where users can run Tulip apps. Tulip player allows you to create a more seamless user experience by removing the need for a web browser and allows increased IT controls. **Edge Devices** **Edge Devices** are any hardware intended to connect physical things to the cloud. This can include entirely mechanical devices, older machines without network functionality, PLCs, and more. Tulip sells the **Edge IO** and **Edge MC** that interface directly into **Triggers** in a breeze, but Tulip can also support other Edge Devices. **Connector Host** Tulip **Connector Hosts** are designed to allow your Tulip Apps to interface with external systems such as databases, APIs, and machines. **On-Prem Connector Hosts** sit within your network and allow Tulip to interface with SQL databases and APIs that aren't accessible to the cloud. **OPC-UA** **OPC Unified Architecture** is a cross-platform, open-source, IEC62541 standard for data exchange from sensors to cloud applications developed by the OPC Foundation.