Skip to content

Commit e1da9bb

Browse files
committed
add note requested by marketing
1 parent dbb2a9c commit e1da9bb

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

src/guides/regional-segment.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,10 +83,13 @@ Use Segment's custom CIDR `3.251.148.96/29` while authorizing Segment to write i
8383
## Destination support and Regional endpoint availability
8484

8585
> info "Don't see a regional endpoint for a tool you're using?"
86-
> As more of the partner tools you use (Sources and Destinations) start to support a regional endpoint, Segment will update this list. Your contact for that tool should have a timeline for when they're hoping to support regional data ingestion. You can also visit Segment's [support page](https://segment.com/help/contact/) for any Segment-related questions.
86+
> As more of the partner tools you use (Sources, Destinations, and Warehouses) start to support a regional endpoint, Segment will update this list. Your contact for that tool should have a timeline for when they're hoping to support regional data ingestion. You can also visit Segment's [support page](https://segment.com/help/contact/) for any Segment-related questions.
8787
8888
The following integrations marked with a ![Supports EU regional endpoints](/docs/images/supported.svg){:class="inline"} (checkmark) support EU Regional endpoints.
8989

90+
> warning "Integrations available in EU workspaces do not guarantee data residency"
91+
> Before you configure an integration, you should check directly with the integration partner to determine if they offer EU endpoints.
92+
9093
{% include content/regional-integrations-table.md %}
9194

9295
## Source Regional support

0 commit comments

Comments
 (0)