---
title: "IP Ranges"
description: "Learn how Sentry's SaaS product uses IP Ranges for API usage, event ingestion, outbound requests, and more."
url: https://docs.sentry.io/security-legal-pii/security/ip-ranges/
---

# 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.

##### API Access

You can programmatically access this IP range information via our API at `docs.sentry.io/api/ip-ranges`.

## [Dashboard and API](https://docs.sentry.io/security-legal-pii/security/ip-ranges.md#dashboard-and-api)

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

```plaintext
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
```

## [Event Ingestion](https://docs.sentry.io/security-legal-pii/security/ip-ranges.md#event-ingestion)

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

1. The [organization subdomain](https://forum.sentry.io/t/organization-subdomains-in-dsns/9360)
2. Sentry's apex domain

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

```plaintext
35.186.247.156/32
```

Sentry's organization subdomains (`o<number>.ingest.sentry.io` and `o<number>.<location>.ingest.sentry.io`) accept events from a separate set of IP addresses:

```plaintext
34.120.195.249/32
34.120.62.213/32
34.160.81.0/32
34.102.210.18/32
2600:1901:0:5e8a::/64
2600:1901:0:7edb::/64
```

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

```plaintext
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.

## [Outbound Requests](https://docs.sentry.io/security-legal-pii/security/ip-ranges.md#outbound-requests)

In some circumstances the Hosted Sentry infrastructure might send HTTP requests your way. Primarily this is relevant to [*JavaScript Source Maps*](https://docs.sentry.io/platforms/javascript/sourcemaps.md), but also affects things like webhooks and other integrations.

Sentry uses the following IP addresses to make outbound requests:

US Data Storage Location

```plaintext
35.184.238.160/32
104.155.159.182/32
104.155.149.19/32
130.211.230.102/32
```

EU Data Storage Location

```plaintext
34.141.31.19/32
34.141.4.162/32
35.234.78.236/32
```

## [Allowing Access via Nginx](https://docs.sentry.io/security-legal-pii/security/ip-ranges.md#allowing-access-via-nginx)

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`:

```nginx
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;
}
```

## [Allowing Access via Apache](https://docs.sentry.io/security-legal-pii/security/ip-ranges.md#allowing-access-via-apache)

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`:

```apacheconf
<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>
```

## [Email Delivery](https://docs.sentry.io/security-legal-pii/security/ip-ranges.md#email-delivery)

All email is delivered from [SendGrid](https://sendgrid.com/) from the following dedicated, static IP addresses:

```plaintext
167.89.86.73
167.89.84.75
167.89.84.14
```

These IP addresses are only for Sentry use.

## [Uptime Monitoring](https://docs.sentry.io/security-legal-pii/security/ip-ranges.md#uptime-monitoring)

Sentry uses the following IP addresses for uptime checks for all regions:

```plaintext
34.123.33.225
34.41.121.171
34.169.179.115
35.237.134.233
34.85.249.57
34.159.197.47
35.242.231.10
34.107.93.3
35.204.169.245
```

### [Dynamic IP Address Retrieval](https://docs.sentry.io/security-legal-pii/security/ip-ranges.md#dynamic-ip-address-retrieval)

For the most up-to-date list of Uptime Monitoring IP addresses, you can query the following API endpoint:

```plaintext
https://sentry.io/api/0/uptime-ips/
```

This endpoint returns a newline-separated list of all current Uptime Monitoring IP addresses (for all regions) that can be programmatically processed in your allowlist configurations.

##### Note

Uptime Monitoring IP addresses may change over time. If you need to programmatically verify whether a visitor is a Sentry bot, we recommend checking the [user agent](https://docs.sentry.io/product/uptime-monitoring/troubleshooting.md#user-agent) instead.

### [Information for Hosting Providers](https://docs.sentry.io/security-legal-pii/security/ip-ranges.md#information-for-hosting-providers)

If you're a hosting provider (like Vercel, Netlify, or similar platforms), please consider the following guidance regarding Sentry's Uptime Monitoring:

Many organizations use Sentry to monitor the uptime of their websites and applications. When Sentry's monitoring IPs are blocked, it creates false outage alerts for all customers trying to monitor sites on your platform.

**Recommended actions for hosting providers:**

1. Allowlist Sentry's monitoring IP addresses in your platform's security rules
2. Configure your firewall to recognize Sentry's monitoring user agent and IP ranges as legitimate traffic
3. Ensure rate limiting policies do not inadvertently block Sentry's monitoring capabilities
4. Consider implementing automatic updates of allowlisted IPs using our API endpoint

By ensuring Sentry can properly monitor sites on your platform, you'll improve the reliability monitoring experience for all your customers who use Sentry.