From cff0538450aa3e0c87f80a0eee88602c6fdcd313 Mon Sep 17 00:00:00 2001 From: Dmitrii Fedorov Date: Fri, 11 Sep 2026 08:24:47 -0700 Subject: [PATCH 1/2] ref(sentry.io): Mirror IP changes in ip-ranges.mdx Updates docs/security-legal-pii/security/ip-ranges.mdx to match app/api/ip-ranges/ip-ranges.json after #19374: - sentry.io dashboard/API: 34.8.226.60/32, 34.111.148.117/32 - Add Control Silo outbound IPs (35.222.255.47/32, 34.61.215.243/32, 34.71.103.17/32) --- docs/security-legal-pii/security/ip-ranges.mdx | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/security-legal-pii/security/ip-ranges.mdx b/docs/security-legal-pii/security/ip-ranges.mdx index 67ecfafbe2a27..d094b6c2b6980 100644 --- a/docs/security-legal-pii/security/ip-ranges.mdx +++ b/docs/security-legal-pii/security/ip-ranges.mdx @@ -23,7 +23,7 @@ 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 +sentry.io 34.8.226.60/32, 34.111.148.117/32 us.sentry.io 35.186.247.156/32 de.sentry.io 34.36.122.224/32, 34.36.87.148/32 ``` @@ -66,6 +66,14 @@ In some circumstances the Hosted Sentry infrastructure might send HTTP requests Sentry uses the following IP addresses to make outbound requests: +Control Silo + +```plaintext +35.222.255.47/32 +34.61.215.243/32 +34.71.103.17/32 +``` + US Data Storage Location ```plaintext From 14d3507da2bd43c4e9502b1b20a1bc6589666c27 Mon Sep 17 00:00:00 2001 From: "sentry-junior[bot]" <264270552+sentry-junior[bot]@users.noreply.github.com> Date: Fri, 11 Sep 2026 15:30:13 +0000 Subject: [PATCH 2/2] fix(docs): complete outbound IP examples Co-Authored-By: Geoff Goldsmith --- docs/security-legal-pii/security/ip-ranges.mdx | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/security-legal-pii/security/ip-ranges.mdx b/docs/security-legal-pii/security/ip-ranges.mdx index d094b6c2b6980..64e216be5f566 100644 --- a/docs/security-legal-pii/security/ip-ranges.mdx +++ b/docs/security-legal-pii/security/ip-ranges.mdx @@ -99,10 +99,16 @@ To allow access to source maps with Nginx for instance, you can use this locatio location ~ ^/static/dist/(.+)\.map$ { alias /your/path/site/static/dist/$1.map; + allow 35.222.255.47/32; + allow 34.61.215.243/32; + allow 34.71.103.17/32; allow 35.184.238.160/32; allow 104.155.159.182/32; allow 104.155.149.19/32; allow 130.211.230.102/32; + allow 34.141.31.19/32; + allow 34.141.4.162/32; + allow 35.234.78.236/32; deny all; } ``` @@ -115,10 +121,16 @@ To allow access to source maps with Apache you can use this example. It can eith Order deny,allow Deny from all + Allow from 35.222.255.47/32 + Allow from 34.61.215.243/32 + Allow from 34.71.103.17/32 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 + Allow from 34.141.31.19/32 + Allow from 34.141.4.162/32 + Allow from 35.234.78.236/32 ```