diff --git a/src/content/docs/durable-objects/reference/data-location.mdx b/src/content/docs/durable-objects/reference/data-location.mdx
index 2ee026d7ac5b6e..fb776ef7ec05a6 100644
--- a/src/content/docs/durable-objects/reference/data-location.mdx
+++ b/src/content/docs/durable-objects/reference/data-location.mdx
@@ -64,6 +64,12 @@ Note that it is also possible to specify a jurisdiction by creating an individua
 
 Durable Objects, as with any stateful API, will often add response latency as requests must be forwarded to the data center where the Durable Object, or state, is located.
 
+:::note[Compatibility with Jurisdictions]
+
+Location hints will be ignored if a jurisdiction is present.
+
+:::
+
 Durable Objects do not currently change locations after they are created<sup>1</sup>. By default, a Durable Object is instantiated in a data center close to where the initial `get()` request is made. This may not be in the same data center that the `get()` request is made from, but in most cases, it will be in close proximity.
 
 :::caution[Initial requests to Durable Objects]
@@ -105,4 +111,4 @@ Hints are a best effort and not a guarantee. Unlike with jurisdictions, Durable
 
 ## Additional resources
 
-- You can find our more about where Durable Objects are located using the website: [Where Durable Objects Live](https://where.durableobjects.live/).
\ No newline at end of file
+- You can find our more about where Durable Objects are located using the website: [Where Durable Objects Live](https://where.durableobjects.live/).