The PagerDuty Events API, which is used for triggering, acknowledging, and resolving incidents, requires that your system be able to make outbound connections to events.pagerduty.com on TCP ports 80 or 443, depending on whether you would like to send events to PagerDuty via HTTP or HTTPS. Most integrations use HTTPS (TCP port 443).
events.pagerduty.com resolves to multiple IPs, which you can find by querying the A records using
$ dig a +short events.pagerduty.com
In this example, you see that PagerDuty's Events API is accessible at the IPs 220.127.116.11, 18.104.22.168, and 22.214.171.124.
To access our REST API, your system must be able to make outbound connections to
<subdomain>.pagerduty.com or api.pagerduty.com on TCP port 443. Our REST API only allows HTTPS connections; HTTP connections are not allowed for security.
<subdomain>.pagerduty.com and api.pagerduty.com usually resolve to multiple IPs as well, however these IPs will be different than the ones used for our Events API or webhooks.
$ dig a +short api.pagerduty.com
In this example, you see that PagerDuty's REST API is accessible at the IPs 126.96.36.199, 188.8.131.52, and 184.108.40.206.
Webhooks are HTTP or HTTPS calls sent from PagerDuty to your web server on the IP and port of your choosing. The current list of IPs that our webhooks are sent from can be found by querying the A records for webhooks.pagerduty.com.
$ dig a +short webhooks.pagerduty.com
In this example, you see that PagerDuty is sending webhooks from the IPs 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, and 184.108.40.206.
Please be aware that the IPs above are only example DNS queries, and do not necessarily reflect the current IPs in use. These IPs can change at any time without warning. If we were to change IPs and your firewall policies were not updated, you will not be able to reach our API endpoints and/or you will stop receiving webhooks from PagerDuty.
If you are hardcoding IPs into your firewall, you can use a script to receive updates when the A records for these hostnames change, or perform lookups on the aforementioned hostnames regularly to update your configurations.