IP Ranges

Learn how Sentry's SaaS product uses IP Ranges for API usage, event ingestion, outbound requests, and more.

Sentry's dashboard and API are both served from different domains, depending on your organization's data storage location. The IP addresses are:

Copied
sentry.io 35.186.247.156/32
us.sentry.io 35.186.247.156/32
de.sentry.io 34.36.122.224/32, 34.36.87.148/32

Sentry's Event Ingestion respects two domains within a Data Source Name (DSN):

  1. The organization subdomain
  2. Sentry's apex domain

Sentry's apex domain (sentry.io) accepts events from the same IP address as the Dashboard and API:

Copied
35.186.247.156/32

Sentry's organization subdomains (o<number>.ingest.sentry.io and o<number>.us.ingest.sentry.io) accept events from a separate IP address:

Copied
34.120.195.249/32

Sentry's organization subdomains in the EU (o<number>.ingest.de.sentry.io) accept events from:

Copied
34.120.62.213/32
130.211.36.74/32

Sentry's legacy ingestion hostname (app.getsentry.com) accepts events from a separate IP address:

Copied
34.96.102.34/32

Organizations in the EU Data Storage Location are unable to ingest events via sentry.io or app.getsentry.com. You can use o<number>.ingest.de.sentry.io instead.

In some circumstances the Hosted Sentry infrastructure might send HTTP requests your way. Primarily this is relevant to JavaScript Source Maps, but also affects things like webhooks and other integrations.

Sentry uses the following IP addresses to make outbound requests:

US Data Storage Location

Copied
35.184.238.160/32
104.155.159.182/32
104.155.149.19/32
130.211.230.102/32

EU Data Storage Location

Copied
34.141.31.19/32
34.141.4.162/32
35.234.78.236/32

To allow access to source maps with Nginx for instance, you can use this location example. This example assumes your source maps live in /static/dist:

Copied
location ~ ^/static/dist/(.+)\.map$ {
    alias /your/path/site/static/dist/$1.map;

    allow 35.184.238.160/32;
    allow 104.155.159.182/32;
    allow 104.155.149.19/32;
    allow 130.211.230.102/32;
    deny all;
}

To allow access to source maps with Apache you can use this example. It can either go into your .htaccess or global config. This example assumes your source maps live in /static/dist:

Copied
<FilesMatch "\.map$">
    Order deny,allow
    Deny from all
    Allow from 35.184.238.160/32
    Allow from 104.155.159.182/32
    Allow from 104.155.149.19/32
    Allow from 130.211.230.102/32
</FilesMatch>

All email is delivered from SendGrid from the following dedicated, static IP addresses:

Copied
167.89.86.73
167.89.84.75
167.89.84.14

These IP addresses are only for Sentry use.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").