IP Ranges
Note
The contents of this page apply only to Sentry's SaaS product. It does not apply to self-hosted or single tenant.
Sentry's dashboard and API are both served from a single IP address for all web traffic. The IP address is:
35.186.247.156/32
Sentry's Event Ingestion respects two domains within a Data Source Name (DSN):
- The organization subdomain
- Sentry's apex domain
Sentry's apex domain (sentry.io
) accepts events from the same IP address as the Dashboard and API:
35.186.247.156/32
Sentry's organization subdomains (o<number>.ingest.sentry.io
) accept events from a separate IP address:
34.120.195.249/32
Sentry's legacy ingestion hostname (app.getsentry.com
) accepts events from a separate IP address:
34.96.102.34/32
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:
35.184.238.160/32
104.155.159.182/32
104.155.149.19/32
130.211.230.102/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
:
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
:
<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:
167.89.86.73
167.89.84.75
167.89.84.14
These IP addresses are only for Sentry use.
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").