Skip to content

Commit b5aecd5

Browse files
gaprllucas-zimerman
authored andcommitted
add new section on info for hosting providers on uptime's ip ranges (#13460)
1 parent 0998f53 commit b5aecd5

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

docs/security-legal-pii/security/ip-ranges.mdx

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -161,3 +161,18 @@ This endpoint returns a newline-separated list of all current Uptime Monitoring
161161
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/uptime-monitoring/troubleshooting/#user-agent) instead.
162162

163163
</Alert>
164+
165+
### Information for Hosting Providers
166+
167+
If you're a hosting provider (like Vercel, Netlify, or similar platforms), please consider the following guidance regarding Sentry's Uptime Monitoring:
168+
169+
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.
170+
171+
**Recommended actions for hosting providers:**
172+
173+
1. Allowlist Sentry's monitoring IP addresses in your platform's security rules
174+
2. Configure your firewall to recognize Sentry's monitoring user agent and IP ranges as legitimate traffic
175+
3. Ensure rate limiting policies do not inadvertently block Sentry's monitoring capabilities
176+
4. Consider implementing automatic updates of allowlisted IPs using our API endpoint
177+
178+
By ensuring Sentry can properly monitor sites on your platform, you'll improve the reliability monitoring experience for all your customers who use Sentry.

0 commit comments

Comments
 (0)