Search results for "{{ search.query }}"

No results found for "{{search.query}}". 
View All Results

Whitelisting IPs

Events API

The PagerDuty Events API, which is used for triggering, acknowledging, and resolving incidents, requires that your system be able to make outbound connections to 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). resolves to multiple IPs, which you can find by querying the A records using dig or nslookup.

Example Query 1

$ dig a +short

In this example, you see that the Events API is accessible at the IPs,, and


To access our REST API, your system must be able to make outbound connections to <subdomain> or on TCP port 443. Our REST API only allows HTTPS connections; HTTP connections are not allowed for security.

<subdomain> and usually resolve to multiple IPs as well, however these IPs will be different than the ones used for our Events API or webhooks.

Example Query 2

$ dig a +short

In this example, you see that the REST API is accessible at the IPs,, and


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 obtained via a HTTPS GET request to the following URL:

The response will be a JSON-encoded list of IP addresses.

Example Query

curl -s

Updating ACLs to Account for Changes

These IPs can change at any time without warning.

Please be aware that the IPs above are only examples, and do not necessarily reflect the current IPs in use. 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.

Whitelisting IPs