IP transit, backhaul and addressing
An operator that builds its own access still needs to carry that traffic to its core, reach the internet, and address its subscribers. Netavo provides all three, from its own core network.
Three services
| Service | What it is | Suited to |
|---|---|---|
| IP transit | Resilient internet transit over IPv4 and IPv6, with BGP | Operators with their own address space and autonomous system |
| Backhaul | Carriage of traffic from exchanges and access networks to your core, and between your own sites and datacentres | Altnets, fibre builders and wireless ISPs reaching a core location |
| IPv4 and IPv6 addressing | Address space provided for your subscribers | ISPs that have no address space of their own |
Where we hand over
Transit and backhaul are handed over in London and Manchester, at three datacentres, on 1G, 10G or 100G ports. Capacity and routing are agreed between your engineers and ours.
About our network →- LondonTelehouse North and Telehouse East
- ManchesterPulsant Manchester
- Port speeds1G, 10G and 100G
- RoutingBGP, over IPv4 and IPv6
Backhaul for an access network
An altnet's fibre, or a wireless ISP's masts, end somewhere short of the operator's core. Backhaul carries that traffic the rest of the way: from exchanges and access networks to your core location, and between your own sites and datacentres.
It is designed around the network you have built, and not around a standard product.
- FromExchanges and access networks
- ToYour core, sites and datacentres
- DesignedAround your own network
Addressing, with or without your own
An operator with its own address space and autonomous system announces it through us over BGP. An ISP with neither can be provided with IPv4 and IPv6 addresses for its subscribers.
Where public IPv4 addresses are scarce, carrier-grade NAT lets many subscribers share them. It is included with Netavo BNG, with port-block logs recording which subscriber held which address and ports.
Netavo BNG →- Your own address spaceAnnounced over BGP
- None of your ownIPv4 and IPv6 provided
- Sharing IPv4CGNAT, included with Netavo BNG
A network that peers
Netavo operates AS208802. It is a member of LINX, peering on LON1 and LON2 with an open peering policy, and a member of the RIPE NCC.
- Autonomous systemAS208802
- LINXLON1 and LON2, open peering policy
- RIPE NCCMember
How a service is delivered
Design
Destinations, capacity, addressing and the handover are agreed with your engineers around your own network.
Deliver
Interconnects are provisioned and tested with your engineers, with a planned migration of existing traffic where required.
Operate
The service is monitored continuously, with proactive fault management and direct access to the engineering team.
Discuss transit or backhaul
Tell us where your network is present and what capacity you need. An engineer will respond with a recommended design and partner pricing.
Work with us →