Firewall settings to receive events in SIGNL4

PLEASE CHECK THE ANNOUNCMENT AT THE END OF THIS ARTICLE!

This article describes how you need to configure your firewall to send/receive events to/from SIGNL4.

a) Web portal, REST API & Webhook traffic to SIGNL4 (HTTPS, Layer 7)

HTTPS web traffic is handled via IP 20.160.37.197 on port 443 (TLS).

For example, if you are not receiving alerts, because your systems cannot connect to SIGNL4 from within your network, it could be due to a firewall configuration preventing 3rd party systems, such as SCOM, to reach the SIGNL4 Webhook or REST API. In this case please make sure your firewall allows traffic to the beforementioned IP/port.

b) Email traffic to SIGNL4 (SMTP, Layer 7)

If you integrate your systems via SMTP email with SIGNL4, make sure to allow traffic to IP 40.114.193.136 on these ports:
25
587
465

On the various email ports we e.g. support these kind of security handshakes:

c) Webhook notifications from SIGNL4

If you have registered your HTTPS endpoints to receive outbound webhook notifications from SIGNL4, that traffic always originates from IP 40.114.193.136.

Upcoming additional IP - please change your firewall settings

The SIGNL4 infrastructure is continuously being expanded and enhanced. As a result, we will soon be using an additional IP address.

What is the additional IP address?

The additional IP address is 128.251.207.225.

When will the additional IP address be used?

The transition will begin no earlier than April 28, 2025. Please update your firewalls accordingly by then.

What traffic is affected?

The additional IP address will affect sections b and c:

• Receiving emails by SIGNL4
  • For example, when your third-party systems send incident notifications to SIGNL4.
    The additional IP address will be the destination IP of this traffic.
• Sending emails by SIGNL4
  • For example, notifications about incidents to your SIGNL4 users via email.
    The additional IP address will be the source IP of this traffic.
• Webhook notifications from SIGNL4
  • For example, when SIGNL4 sends HTTP notifications to your third-party systems about changes within a SIGNL4 team.
    The additional IP address will be the source IP of this traffic.