Overview
When connecting Rootly to your internal systems or third-party services, you may need to allow traffic from Rootly’s outbound IP addresses. Rootly uses a fixed set of outbound IP addresses for:- Integration traffic
- Outbound webhook delivery
Security Considerations
IP whitelisting adds an extra layer of network security by helping you:- Restrict access to trusted IP addresses
- Prevent unauthorized connections from unknown sources
- Meet internal security or compliance requirements
- Protect systems that receive data from Rootly
Rootly Outbound IP Addresses
Add the following IPv4 addresses to your allowlist:Production IP Addresses
These addresses are used for both integration traffic and outbound webhook delivery.
IP Address Stability: These production IP addresses are permanent and will not change. You can safely use them in long-term firewall rules and security policies.
Common Use Cases
Webhook Endpoints
If Rootly sends webhooks to your systems:- Whitelist both IP addresses on the receiving endpoint
- Ensure your endpoint accepts HTTPS traffic
- Verify your SSL certificates are valid
API Access
If Rootly makes API calls to your services:- Update firewall or load balancer rules to allow these IPs
- Confirm your API gateway accepts traffic from both addresses
- Test connectivity after making changes
Testing Your Configuration
After updating your allowlist:- Verify integration connectivity in Rootly
- Check integration or delivery logs for connection errors
- Test webhook delivery if applicable
- Review firewall or security logs to confirm traffic is allowed
Getting IP Ranges via API
You can also retrieve the current IP ranges programmatically using Rootly’s IP ranges API. The API returns:integrations_ipv4integrations_ipv6webhooks_ipv4webhooks_ipv6