getsentry · BojanOro · May 25, 2026
diff --git a/develop-docs/application-architecture/multi-region-deployment/control-silo.mdx b/develop-docs/application-architecture/multi-region-deployment/control-silo.mdx
@@ -7,7 +7,7 @@ Within the Control Silo are features that allow us to provide backwards compatib
 
 # API Gateway
 
-Prior to our multi-region offering, all API traffic from customers would be sent to [sentry.io](http://sentry.io) . We need to continue supporting these URLs despite some customers residing in the `us` region and others in the `de` region. The API Gateway functionality of control silo will introspect requests and proxy requests to the appropriate region based on path parameters in the request. Requests can be routed via:
+Prior to our multi-region offering, all API traffic from customers would be sent to [sentry.io](http://sentry.io) . We need to continue supporting these URLs despite some customers residing in the `us` region and others in the `us2`, or `de` regions. The API Gateway functionality of control silo will introspect requests and proxy requests to the appropriate region based on path parameters in the request. Requests can be routed via:
 
 - Organization slug or id
 - Sentry App Installation UUID

diff --git a/develop-docs/application-architecture/overview.mdx b/develop-docs/application-architecture/overview.mdx
@@ -115,6 +115,7 @@ In addition to the siloed modes, there also exists a **Monolith** mode. In monol
 ```mermaid
 flowchart TD
   ui[Frontend UI] --> usr
+  ui --> us2r
   ui --> cs
   ui --> eur
 
@@ -123,6 +124,11 @@ flowchart TD
     usapi --> used[(US Event Data)]
   end
 
+  subgraph us2r [US2 Region]
+    us2api[US2 Sentry API] --> us2pg[(US2 Postgres)]
+    us2api --> us2ed[(US2 Event Data)]
+  end
+
   subgraph cs [Control Silo]
     capi[Control Silo Sentry API] --> cpg[(Control Postgres)]
   end
@@ -140,6 +146,6 @@ Each region silo can be scaled independently, and is isolated from other regions
 Silo modes are defined as environment variables (and django settings). The relevant settings are:
 
 - `SILO_MODE` either `CONTROL`, `REGION` , `MONOLITH` or None.
-- `SENTRY_REGION` The name of the region the application is in (eg. `us` or `de`) or `None`.
+- `SENTRY_REGION` The name of the region the application is in (eg. `us`, `us2`, or `de`) or `None`.
 - `SENTRY_REGION_CONFIG` A list of regions that the application has. This list defines names, URLs, and category (multiregion, singletenant) that a region operates as.
 - `SENTRY_MONOLITH_REGION` The region name of the former ‘monolith’ region. For [sentry.io](http://sentry.io) this is the `us` region. The monolith region has special behavior that is required for backwards compatibility.
diff --git a/docs/api/index.mdx b/docs/api/index.mdx
@@ -28,8 +28,10 @@ The current version of the Sentry's web API is considered **v0**. Our public end
 
 While many of our APIs use `sentry.io` as the host for API endpoints, if
 you want to indicate a specific [data storage location](/organization/data-storage-location/#what-types-of-data-are-stored-where), you should use region-specific domains.
+Picking the correct region-specific domain will generally result in lower latency for most API calls.
 
 - US region is hosted on `us.sentry.io`
+- US2 region is hosted on `us2.sentry.io`
 - DE region is hosted on `de.sentry.io`.
 
 To find out which API resources are available on region-based domains, see [what

diff --git a/docs/organization/data-storage-location/index.mdx b/docs/organization/data-storage-location/index.mdx
@@ -10,20 +10,23 @@ You can choose where to store your data when you’re setting up your Sentry acc
 
 **Please note that once selected, your data storage location can’t be changed. The only way to switch it is by creating a new organization.**
 
+New US organizations may automatically be placed in the US2 region. You can check which region your organization is in by viewing your organization’s settings page.
+
 Your selection determines your data storage location only. Sentry will continue to access and process your data in accordance with your agreement with Sentry for the Sentry service and our [Privacy Policy](https://sentry.io/privacy/).
 
 The table below shows the location where your data will be stored at rest, based on your selection.
 
-| **Data Storage Location**     | **Physical Location** |
-| ----------------------------- | --------------------- |
-| United States of America (US) | Iowa, USA             |
-| European Union (EU)           | Frankfurt, Germany    |
+| **Data Storage Location**     | **Region** | **Physical Location**  |
+| ----------------------------- | ---------- | ---------------------- |
+| United States of America (US) | US         | Iowa, USA              |
+| United States of America (US) | US2        | Las Vegas, Nevada, USA |
+| European Union (EU)           | EU         | Frankfurt, Germany     |
 
 ## What Types of Data Are Stored Where
 
 Here’s a list of the types of data that will be stored in whichever data storage location (US or EU) you select.
 
-### Data Stored In Selected Location (US or EU)
+### Data Stored In Selected Location (US, US2, or EU)
 
 - Error events, activity, and issue links
 - Transactions
@@ -36,7 +39,7 @@ Here’s a list of the types of data that will be stored in whichever data stora
 
 ### Data Stored in US
 
-Here’s a list of the types of data that may be stored in the US.
+Here’s a list of the types of data that may be stored in the US, regardless of your selected Data Storage Location.
 
 - User accounts, notification settings, and 2FA authenticators
   (User accounts are shared by many organizations.)
@@ -54,11 +57,11 @@ Here’s a list of the types of data that may be stored in the US.
 
 Metadata that lets Sentry identify an organization will be replicated out of the organization's data storage location to facilitate login, and backwards-compatible APIs. You can always confirm the location of your organization by viewing your organization's settings page.
 
-If you choose to share data in a support ticket, chat or other support interaction, the data will be stored in the US.   
+If you choose to share data in a support ticket, chat or other support interaction, the data will be stored in the US.
 
-### Data Stored in All Locations (US and EU)
+### Data Stored in All Locations (US, US2, and EU)
 
-Here’s a list of the types of data that will be stored in both data storage locations (US and EU).
+Here’s a list of the types of data that will be stored in all data storage locations (US, US2, and EU).
 
 - Uptime checks
 
@@ -72,10 +75,11 @@ For uptime monitoring to work effectively, we perform uptime checks from multipl
 
 To ensure that your API requests are only processed within your selected data storage location, use the region-specific domain:
 
-| **Data Storage Location**     | **API domain** |
-| ----------------------------- | -------------- |
-| United States of America (US) | us.sentry.io   |
-| European Union (EU)           | de.sentry.io   |
+| **Data Storage Location**     | **Region** | **API domain** |
+| ----------------------------- | ---------- | -------------- |
+| United States of America (US) | US         | us.sentry.io   |
+| United States of America (US) | US2        | us2.sentry.io  |
+| European Union (EU)           | EU         | de.sentry.io   |
 
 For [data stored in the US](#data-stored-in-us), your API domain should be `sentry.io`.