-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Update IP ranges documentation for Sentry's Uptime Monitoring, including dynamic IP retrieval and guidance for hosting providers #13458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -58,7 +58,6 @@ 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 | ||
|
|
||
| In some circumstances the Hosted Sentry infrastructure might send HTTP requests your way. Primarily this is relevant to [_JavaScript Source Maps_](/platforms/javascript/sourcemaps/), but also affects things like webhooks and other integrations. | ||
|
|
@@ -127,29 +126,47 @@ These IP addresses are only for Sentry use. | |
|
|
||
| ## Uptime Monitoring | ||
|
|
||
| Sentry uses the following IP addresses for uptime checks: | ||
|
|
||
| US | ||
| 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 | ||
| ``` | ||
|
|
||
| EU | ||
|
|
||
| ```plaintext | ||
| 34.159.197.47 | ||
| 35.242.231.10 | ||
| 34.107.93.3 | ||
| 35.204.169.245 | ||
| ``` | ||
|
|
||
| ### 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://us.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. | ||
|
|
||
| <Alert title="Note" level="warning"> | ||
|
|
||
| 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](/product/alerts/uptime-monitoring/troubleshooting/#user-agent) instead. | ||
|
|
||
| </Alert> | ||
|
|
||
| ### 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 | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We probably don't want to recommend looking at the user agent -- since this can be spoofed |
||
| 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. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.