Mendix IP Addresses
Introduction
An IP address is the address of a device on an internet or local network, written in a format that other devices can understand. The IP address can be used to locate, identify, and communicate with that device on the network.
Definitions
Mendix uses one IP address when someone connects to your Mendix application (incoming IP) and a different IP address when your application connects to outside services (outgoing IP).
Incoming IP addresses are liable to change without notice and should not be used to access the application.
Mendix maintains the current outgoing IP addresses as much as possible. However, the outgoing addresses may change for operational reasons. At least 48 hours before any changes, Technical Contacts will be emailed and a notification will be listed on Mendix Platform Status.
Incoming IP
This is the IP address of one of Mendix's front-facing web servers. It is the IP address your browser connects to when you visit your application in Mendix Cloud (for example, when you go to yourapplication.mendixcloud.com).
You can retrieve this IP address by performing a DNS lookup for the domain. To do so, you can use a free DNS lookup service such as http://ping.eu/nslookup/.
Outgoing IP
This is the IP address other servers see when the Mendix application initiates the connection. You normally need to add it to your firewall if you want your Mendix application to contact one of your firewalled servers.
Ranges
Mendix Cloud
Mendix uses the following static IP addresses. If you need more information, file a support ticket with Mendix Support.
| Region | Location | IP Addresses | Default URL |
|---|---|---|---|
| Mendix Cloud Free Tier EU | Ireland (eu-west-1) | 52.18.20.11952.18.122.23852.211.106.230 | {app-name}-sandbox.mxapps.ioor {app-name}.mxapps.io |
| Mendix Cloud Africa | Cape Town (af-south-1) | 13.245.222.8113.246.150.20913.246.181.69 | {app-name}.apps.af-1a.mendixcloud.comor {app-name}-{environment-type}.apps.af-1a.mendixcloud.com |
| Mendix Cloud Asia Pacific | Singapore (ap-southeast-1) | 52.77.0.5254.179.212.86122.248.194.24 | {app-name}.apps.ap-2a.mendixcloud.comor {app-name}-{environment-type}.apps.ap-2a.mendixcloud.com |
| Mendix Cloud Asia Pacific | Sydney (ap-southeast-2) | 13.54.176.5813.54.220.14313.238.3.124 | {app-name}.apps.au-1a.mendixcloud.comor {app-name}-{environment-type}.apps.au-1a.mendixcloud.com |
| Mendix Cloud Asia Pacific | Tokyo (ap-northeast-1) | 13.113.58.1552.193.228.152.198.238.110 | {app-name}.mendixcloud.comor {app-name}-{environment-type}.mendixcloud.com |
| Mendix Cloud Asia Pacific | Mumbai (ap-south-1) | 43.204.254.9543.205.31.3265.1.183.103 | {app-name}.apps.ap-3a.mendixcloud.comor {app-name}-{environment-type}.apps.ap-3a.mendixcloud.com |
| Mendix Cloud Asia Pacific | Osaka (ap-northeast-3) | 15.168.59.12013.208.255.6415.152.172.188 | {app-name}.apps.ja-2a.mendixcloud.comor {app-name}-{environment-type}.apps.ja-2a.mendixcloud.com |
| Mendix Cloud Asia Pacific | Seoul (ap-northeast-2) | 3.35.61.1753.35.153.9043.200.98.224 | {app-name}.apps.ap-4a.mendixcloud.comor {app-name}-{environment-type}.apps.ap-4a.mendixcloud.com |
| Mendix Cloud Asia Pacific | Jakarta (ap-southeast-3) | 108.137.164.15643.218.102.8643.218.75.101 | {app-name}.apps.ap-5a.mendixcloud.comor {app-name}-{environment-type}.apps.ap-5a.mendixcloud.com |
| Mendix Cloud Canada | Canada (ca-central-1) | 3.97.111.1243.98.194.5435.182.171.81 | {app-name}.apps.ca-1a.mendixcloud.comor {app-name}-{environment-type}.apps.ca-1a.mendixcloud.com |
| Mendix Cloud EU: AWS Frankfurt | Frankfurt (eu-central-1) | 35.156.112.2835.157.102.1452.58.42.15 | {app-name}.mendixcloud.comor {app-name}-{environment-type}.mendixcloud.com |
| Mendix Cloud EU: AWS Frankfurt | Frankfurt-2 (eu-central-1) | 3.76.96.2523.125.228.15154.93.126.19 | {app-name}.apps.eu-1c.mendixcloud.comor {app-name}-{environment-type}.apps.eu-1c.mendixcloud.com |
| Mendix Cloud EU: AWS Ireland | Ireland (eu-west-1) | 52.18.10.6252.208.39.9999.80.177.69 | {app-name}.mendixcloud.comor {app-name}-{environment-type}.mendixcloud.com |
| Mendix Cloud Middle East | Bahrain (me-south-1) | 15.184.118.25316.24.5.102157.241.15.222 | {app-name}.apps.me-1a.mendixcloud.comor {app-name}-{environment-type}.apps.me-1a.mendixcloud.com |
| Mendix Cloud Middle East | UAE (me-central-1) | 3.29.53.853.29.155.33.29.189.106 | {app-name}.apps.me-2a.mendixcloud.comor {app-name}-{environment-type}.apps.me-2a.mendixcloud.com |
| Mendix Cloud SA | São Paulo (sa-east-1) | 15.229.194.12454.232.11.167177.71.150.202 | {app-name}.apps.sa-1a.mendixcloud.comor {app-name}-{environment-type}.apps.sa-1a.mendixcloud.com |
| Mendix Cloud UK | London (eu-west-2) | 18.130.169.1535.177.185.4752.56.174.215 | {app-name}.mendixcloud.comor {app-name}-{environment-type}.mendixcloud.com |
| Mendix Cloud US | North Virginia (us-east-1) | 34.197.224.25052.55.243.6252.205.207.103 | {app-name}.mendixcloud.comor {app-name}-{environment-type}.mendixcloud.com |
| Mendix Cloud US | Oregon (us-west-2) | 35.160.4.2944.236.131.8854.190.172.197 | {app-name}.apps.us-2a.mendixcloud.comor {app-name}-{environment-type}.apps.us-2a.mendixcloud.com |
Accessing AWS Services in Mendix Cloud
Mendix Cloud uses VPC endpoints to privately access AWS services. The aws:VpcSourceIp condition key can be used in a policy to allow principals (Mendix apps and end-users) to make requests only from within a specified IP range.
If you apply IP restrictions to your AWS IAM user or role, you must ensure that the following IP ranges for API requests are allowed in your policy:
For Mendix apps deployed to the Cloud Foundry infrastructure:
10.10.128.0/2110.10.136.0/2110.10.144.0/21
For Mendix apps deployed to the Kubernetes infrastructure:
10.11.64.0/1810.11.128.0/1810.11.192.0/18
To find whether your app uses Kubernetes or Cloud Foundry, go to Apps and check the Infrastructure label for your environment.
Mendix Portal
Some services running on Mendix Portal (such as the PDF Document Generation service) use a fixed set of inbound and outbound IP addresses. If you use these services and apply IP restrictions to your app, you must ensure that the IP addresses listed below are allowed in your policy.
Outgoing IP
- 18.194.214.35
- 52.59.169.126
- 3.64.82.159
Incoming IP
- 52.223.19.148
- 76.223.74.135
Frequently Asked Questions
Why Does the Outgoing IP Address Need to Change?
Because Mendix provides a platform, the infrastructure needs to remain flexible. Mendix maintains the current outgoing IP addresses as much as possible. However, the outgoing addresses may occasionally change for operational reasons. Any changes are subject to a 48-hour notice period.
In the Past, We Have Received the Same IP Address for Multiple Environments and Applications. How Is That Possible?
The incoming IP address is the same for multiple environments and applications because it is the IP address of a front-facing web server. The web server serves multiple applications.
The outgoing IP address is the same for multiple environments and applications because Mendix uses network address translation (NAT) on its routers.
Which IP Address Should Be Safelisted on Our Firewall?
Usually, you configure your firewall with rules for incoming traffic to your network. Therefore, you need to use the outgoing IP address of the Mendix application.