Home network and visited network in roaming
The home network is the network that holds a subscriber relationship and manages the core identity of the SIM or eSIM. The visited network is the network that a device uses when it connects outside that home environment. In roaming, the two roles work together so that a device can keep service while it is away from its usual network.
In plain terms, the home network decides who the subscriber is and whether roaming should be allowed, while the visited network provides the radio access and local connection. This page uses those terms in the general roaming sense, which is the basis for mobile roaming and for many roaming networks used by voice, data, and messaging services. For a broader framework, see mobile roaming explained.
What the home network does
The home network is the network associated with the subscriber profile. It stores the identity data needed to recognise the device, check whether service is permitted, and apply the rules that belong to that line or profile. It is also the place where roaming agreement logic is anchored, even when the device is physically connected elsewhere.
When a device leaves its usual coverage area, the home network remains the reference point for authentication and service control. That is why the phrase home network vs visited network is about function rather than geography alone. The home side remains responsible for the subscriber relationship, while the visited side becomes the local point of access.
What the visited network does
The visited network is the network that the device actually reaches on the ground. It detects the device, accepts or rejects the connection attempt, and carries traffic once the roaming relationship is in place. The visited network explained simply is the local network that supplies the signal and the path into its radio system, then hands the session into the wider roaming arrangement.
Roaming networks are therefore not a single network, but a chain of coordinated systems. The visited network provides access, while the home network confirms the subscriber and supervises the service relationship. In practice, that division is what allows a device to attach to a network abroad without becoming a local subscriber there.
How the connection is established
When a device tries to connect, it sends identity information from the SIM, eSIM, or iSIM profile. The visited network forwards that information through roaming signalling so that the home network can verify it. If the identity is accepted, the visited network opens the radio session and the device can use service through that local access point.
This flow is central to roaming authentication and login explained in network terms. Authentication proves that the device is allowed to attach, while login in this context is the process of being admitted to service on the visited network. The exact path may differ by technology, but the principle remains the same: the visited network carries the traffic, and the home network authorises the subscriber.
roaming authentication is one of the key control points in this process, because it links identity, policy, and access before service begins.
Why the distinction matters
Knowing the difference between home network and visited network helps explain many roaming behaviours. It clarifies why a device may attach successfully yet still have restricted service, why signalling must cross network boundaries, and why the subscriber relationship does not move just because the device is travelling. It also helps with device management in complex environments such as IoT and multi-profile deployments.
For network planners and service teams, the distinction is useful when tracing failures, analysing roaming records, and understanding where responsibility sits in the service chain. That practical view is also reflected in roaming operations tools used by growing MVNOs, where agreement handling and device settings must stay aligned across many partners. See roaming tools for a general overview of that workflow.
Practical takeaway
The simplest way to think about the two terms is this: the home network owns the subscriber relationship, and the visited network provides the local access. If service behaves unexpectedly while roaming, this split is usually the first thing to examine, because it shows where identity is checked, where access is granted, and where the traffic actually enters the network.
For readers building a mental model of roaming, this guide is most useful as a foundation. Once the home and visited roles are clear, the wider roaming process becomes easier to understand, including agreement handling, authentication, and session control. A related technical layer is covered in session setup, which shows how a roaming connection moves from attachment into usable service.