The short version
What is an Internet handoff?
The handoff is the agreed connection point where an Internet provider delivers service to a customer’s network. It might be an Ethernet port on provider equipment or a fiber connection at a panel. Your router or firewall connects to that point using the physical and network settings agreed with the provider.
The provider and your IT team each prepare one side. Both need to agree on the connector, speed, addressing, and who supplies the equipment.
The handoff and the service boundary should be documented. They do not necessarily tell you the full scope of an SLA; read the service agreement for that.
01 / The connection
Follow the path into your office.
A typical path may run from the provider’s network, through a building entrance and riser, to a fiber panel or provider device in an equipment room. A patch cable then connects the handoff to your router or firewall. The physical arrangement varies by building and service.
Provider side
The network and equipment the provider operates, up to the agreed handoff.
Customer side
The router or firewall, local network, power, and other equipment your team manages, as specified in the agreement.
Ask who supplies and maintains the patch cable, optical module, and any cross-connect. A cross-connect may be a separately arranged cable between facilities in a building or data center. Do not assume it is included or that every installation uses one.
02 / The physical details
Make sure the two sides can connect.
Ethernet is a common handoff. It can use copper or optical fiber, depending on the equipment and agreed service. A port’s shape alone does not establish that it supports the intended speed or signal.
| Confirm | Why it matters |
|---|---|
| Port and speed | Identify the required Ethernet speed and an available, compatible interface. The port rate and purchased service rate can differ. |
| Copper or fiber | Confirm the media, connector, required distance, and cable. Optical connections may use single-mode or multimode fiber, depending on the optics. |
| Optical modules | Confirm the form factor, Ethernet standard, wavelength, reach, and device compatibility. Matching the form factor alone is not enough. |
| Fiber connector and polarity | Agree on connector type and fiber count; transmit and receive paths must match the design. Some optics use one strand, others use two or more. |
| Location and ownership | Identify the room, rack, panel, port, power, and person responsible for each component. |
03 / The network settings
A cable is only the beginning.
Your provider should supply the information needed for the specific service. Depending on the design, that can include an IPv4 address and prefix, default gateway, IPv6 addressing, DNS resolver information, a VLAN identifier, MTU, and routing details. Some settings may be assigned automatically; others need to be entered by your network administrator.
Confirm whether traffic is untagged or uses a particular VLAN, and whether both ends use compatible speed, auto-negotiation, and other link settings. MTU is the maximum IP packet size supported by the interface or path. A mismatch can cause applications to fail in ways that are not obvious from a link light.
A service may use a default route, static routes, or BGP. Use only the configuration and addresses provided for your connection; coordinate changes and keep a rollback plan. Our business IP address guide explains subnets, gateways, and IPv6.
04 / Put it together
A handoff worksheet.
For a 10 Gbps example, an IT team might confirm a compatible 10 Gigabit Ethernet port on its firewall, the optical standard and connector on each side, and the location of the panel. They would also confirm the assigned IP settings, any VLAN tagging, and the route used to reach the provider.
This is an illustration, not a standard specification for every service. Before installation, ask both the provider and device vendor to confirm the exact optics, cable, port, and configuration that work together.
05 / Turn-up
What should happen on installation day?
- 01
Confirm access and equipment
Have the right people available for the building, equipment room, provider handoff, and customer firewall. Confirm power, cabling, and the planned change window.
- 02
Bring up the link
Check the interface state and negotiated or configured speed. Record the port labels and initial error counters.
- 03
Verify service
Check the assigned addressing, routing, DNS, and representative applications. Coordinate throughput and latency tests with the provider and use capable equipment.
- 04
Document the handoff
Save the provider’s circuit identifier, contact information, interface and cabling details, settings, test results, and escalation procedure.
06 / First checks
If it does not connect.
If the link is down, check power, the correct port, device compatibility, cabling, optics, and interface status on both ends with the responsible teams. If the link is up but traffic fails, check VLAN tagging, addresses, gateway, routing, firewall policy, and DNS. An illuminated link does not prove that the rest of the service is working.
Review interface counters for errors or drops on the customer adapter and along the path to the handoff, and record when counters were last cleared. Share observations and timestamps rather than resetting counters or changing settings without coordination. The latency and packet loss guide offers more ways to investigate.
07 / Before the appointment
Questions to exchange.
- Where exactly is the handoff, and who can access it?
- What are the port speed, media, optical standard, connector, and cable requirements?
- Who provides and supports the optics, patch cable, and any cross-connect?
- Is the service tagged or untagged? What MTU and link settings are required?
- What IPv4 and IPv6 addresses, prefixes, gateways, and routes will be supplied?
- What testing will be performed, and who should attend?
- How are the service boundary, circuit ID, and support responsibilities documented?
About this brief
Sources and further reading.
Product requirements vary by device and service. Consult the current documentation for the equipment and the written handoff specification.
Working with fiber
- Juniper Networks: Maintain fiber-optic cablesHandling and laser safety
- Cisco: Ethernet line card guideExamples of interface and optical specifications
Connecting two networks
- IETF RFC 3021IPv4 /31 prefixes on point-to-point links
- IANA: Number resourcesIPv4 and IPv6 address basics
Prepared by Stealth Communications, a provider of business connectivity. Handoff details and responsibilities depend on the individual service and agreement.