The ERP added to both the Transit and User VPC matches, but none of the...

In an NC2 environment using Flow Virtual Networking (FVN), the External Routable Prefix (ERP) is used to identify the address space that can reach external networks. If the ERP is correctly configured in both the Transit and User VPCs but outbound communication still fails, the issue typically lies within the virtual routing table. A static route (such as 0.0.0.0/0) must be manually added to the User VPC routing table with the next hop set to the overlay-external-subnet. Without this explicit static route, the virtual router within the User VPC does not know how to direct traffic toward the Transit VPC for outbound delivery, even if the address ranges are theoretically compatible. Verifying this routing path is a standard step in ensuring overlay workloads can reach on-premises or internet resources.