Network Connectivity and IP Whitelisting
Some integrations require IP allowlisting or firewall rules to permit outbound connections from RunReveal. This page provides the IP addresses you’ll need to whitelist for integrations that use IP-based access controls.
RunReveal Outbound IP Addresses
Add all of the following IP addresses (primary and fallback) to your whitelist so that connections work during both normal operation and alternat failover. Outbound traffic from RunReveal may originate from any of these IPs:
Primary:
18.190.118.6518.221.211.6718.221.220.90
AWS alternat fallbacks:
These IPs are used as alternate egress when the primary endpoints are unavailable. Whitelist them to avoid connectivity gaps.
3.136.105.2153.134.206.1253.133.26.125
Add all primary and fallback IPs to your whitelist. Primary IP addresses are static and do not change. Fallback IPs may be used during alternat failover, so including every IP above ensures reliable connectivity. If you need to verify these IPs or have questions about network connectivity, contact RunReveal support.
When IP Whitelisting is Required
IP whitelisting is typically required for integrations that:
- Use IP-based network policies (e.g., Snowflake, some database integrations)
- Have firewall rules that restrict inbound connections
- Require allowlisting of specific source IPs for API access
- Use network security groups or access control lists (ACLs)
Common Integration Use Cases
Snowflake
If your Snowflake account has IP allowlisting enabled, add all six RunReveal IP addresses (primary and alternat fallbacks) to your Snowflake network policy. See the Snowflake integration guide for detailed setup instructions.
Database Integrations
For database integrations that require IP whitelisting, add all six IP addresses (primary and alternat fallbacks) to your database’s allowed IP list or firewall rules.
API Integrations with IP Restrictions
Some API integrations may have IP-based access controls. Whitelist all six IP addresses to ensure reliable connectivity, including the alternat fallbacks.
Troubleshooting
If you’re experiencing connection issues with an integration that requires IP whitelisting:
- Verify all six IP addresses (including alternat fallbacks) are whitelisted in your network policy
- Check that firewall rules allow outbound connections from these IPs
- Ensure network security groups or ACLs permit traffic from these IPs
- Review integration-specific documentation for additional network requirements
For additional assistance with network connectivity issues, contact RunReveal support.