diff --git a/pods/troubleshooting/pod-migration.mdx b/pods/troubleshooting/pod-migration.mdx
index 4b93c0f6f..8b927ea28 100644
--- a/pods/troubleshooting/pod-migration.mdx
+++ b/pods/troubleshooting/pod-migration.mdx
@@ -33,6 +33,10 @@ When prompted to migrate your Pod, you have three options:
 
 3. **Automatically migrate Pod data**: This option spins up a new Pod with the same specifications as your current one and automatically migrates your data to a machine with available GPUs. The migration process finds a new machine with your requested GPU type, provisions the instance, and transfers your network volume data from the old Pod to the new one.
 
+<Warning>
+Migration only searches for GPUs in the same datacenter as your [network volume](/storage/network-volumes). The volume can't be moved, so GPUs in other datacenters can't be used with it. If migration returns "no instances currently available" while the same GPU type appears in the general deploy list, those GPUs are in other datacenters. To resolve this, wait for capacity in your volume's datacenter, or create a new network volume in a different datacenter and copy your data over.
+</Warning>
+
 ## Important considerations for migration
 
 When you trigger an automatic Pod migration, you'll receive a new Pod with a new ID and IP address. This is because Pod IDs are architecturally tied to specific physical machines.
diff --git a/storage/network-volumes.mdx b/storage/network-volumes.mdx
index 9e2267bd5..27207a537 100644
--- a/storage/network-volumes.mdx
+++ b/storage/network-volumes.mdx
@@ -9,6 +9,10 @@ Network volumes provide persistent storage that exists independently of your com
 
 Network volumes are backed by high-performance NVMe SSDs with transfer speeds of 200-400 MB/s (up to 10 GB/s peak).
 
+<Note>
+Each network volume lives in a single datacenter and cannot be moved. Any Pod, worker, or Instant Cluster that attaches the volume must run in that same datacenter. This limits the GPU inventory available to those workloads. To spread across datacenters, create a separate volume in each one and copy data between them manually. See [Migrate files between volumes](#migrate-files-between-volumes).
+</Note>
+
 ## Storage tiers
 
 Network volumes are available in two tiers: