monday.com's global network utilizes multiple IP ranges to serve content and initiate TCP/TLS connections with third-parties and on-premise integrations. This allows us to support our architecture's redundancy and security, and can better allow customers to manage their network access to monday.com.
Who can benefit from this information?
We make this information public for network and IT administrators who wish to whitelist monday.com's servers on their firewalls and network choke points. This is particularly useful if you are looking to implement webhook-based on-premise integrations such as Jira, and custom monday.com apps.
monday.com's egress (outbound) IP addresses
|CIDR notation||IP range|
|220.127.116.11/24||18.104.22.168 - 22.214.171.124|
|126.96.36.199/23||188.8.131.52 - 184.108.40.206|
We use these IP addresses to send requests, usually in the form of webhooks, from our internal networks to external ones. When our servers reach out to your on-premise system, the connection will originate from one of these IP ranges.
To ensure monday.com's integrations and apps can reach your hosted application or on-premise network, make sure to whitelist these IP ranges.
Can I whitelist your ingress (inbound) IP addresses?
monday.com uses Cloudflare as a first line of defense for our networks against a variety of attacks and to ensure high availability of our resources. For that reason, we cannot commit to having static IPs that never change.
You can use a tool like dig to resolve the IP addresses of your own slug. While these addresses change rarely, they do change from time to time.
If you have any questions, please reach out to our team by using our contact form. We're available 24/7 and happy to help!