IP transit for networks in the UK and Europe
BGP or static-routed internet connectivity from Exascale AS61049, with capacity and handoff options agreed for your network.
Service at a glance
Exascale IP transit
BGP or static-routed internet connectivity
Internet reachability for ISPs, access networks, data centres and content networks, delivered through Exascale AS61049. The handoff, bandwidth commitment and commercial terms are agreed for your network.
Availability: UK and European points of presence; port and extension availability are confirmed for the requested location.
Routing
BGP and static routing options, with full, partial or default routes according to the agreed configuration.
IP protocols
IPv4 and IPv6 support, with the required address and routing configuration agreed before delivery.
Port capacity
Published port options range from 1 Gbit/s to 400 Gbit/s, with supported link aggregation subject to location and availability.
Contract options
Published term options range from 12 to 60 months. Setup and commercial arrangements are confirmed in the quotation.
Charging basis
Specify committed bandwidth and expected traffic separately from port speed. Agree measurement, burst and overage treatment in the quotation.
Handoff requirements
Provide the site, interface, cross-connect or extension requirements and any routing-resource information needed for delivery.
Connect your network to the wider internet
Global IP reachability with routing options
Exascale supplies IP transit for ISPs, access networks, data centres and content networks. The service combines upstream transit and peering to provide internet reachability, with BGP or static routing to suit your requirements.
Read what IP transit is and who needs it and our BGP guide before defining your handoff. If you are comparing ways to exchange traffic, see peering versus IP transit.
Support for IPv4 and IPv6, available in both dual-stack and non-dual-stack configurations.
We provide the full Internet routing table by default, as well as partial routing options that include all of our bilateral peering relationships with ISPs, network service providers, and content providers across the UK and Europe. Where required, we can also announce a single default route to your BGP capable device.
We support both static routing and BGP. If your equipment does not support BGP, we can statically route your prefixes as required.
We operate a low-latency, high-speed, carrier-grade network that is extensively peered and engineered to maintain at least 50% excess capacity at all times. By proactively scaling capacity and expanding peering relationships as needed, we deliver a consistently uncontended network service to our customers.
Port options range from 1 Gbit/s to 400 Gbit/s, subject to location and availability. Link aggregation can combine supported physical interfaces; specify your port and aggregate-capacity requirements when requesting a quote.
If you choose to use BGP (Border Gateway Protocol) instead of static routing, you may advertise your own IRR-registered resources from RIPE LIR, ARIN, or other registries. We simply require that the appropriate route objects are created in the RIPE Database for your Autonomous System Number (ASN). This enables us to automatically generate and maintain inbound prefix and import filters.
We automatically generate and maintain inbound and outbound prefix filters using authoritative Internet Routing Registry (IRR) data associated with customer ASNs. This approach minimizes the risk of route leaks and configuration errors, accelerates provisioning and updates, and ensures routing policies remain current; delivering greater network stability and security without manual overhead.
Direct peering complements upstream transit when exchanging traffic with participating networks. Routing depends on the destination network, available interconnections and applicable policy.
Exascale applies BGP routing policy across transit and peering connections. Selected paths can change as networks and routing conditions change.
Each Exascale POP is architected with resilience and performance as a baseline requirement, featuring a minimum of two dedicated 100G uplink into the core network. This high-capacity connection ensures that even at entry-level deployments, customers benefit from ample headroom to support rapid traffic growth, bursty workloads, and latency-sensitive applications.
We offer flexible contract options to suit different business needs, with terms available from 12 months up to 60 months. Customers can choose agreements with or without setup fees, depending on whether they prefer lower upfront costs or more favourable long-term pricing.
Choose your handoff and capacity
Port speed and committed bandwidth are different requirements
Specify your required port speed, committed data rate, expected traffic profile and preferred delivery location. Your quotation should identify the bandwidth measurement method, any burst or overage treatment, contract term and setup or cross-connect costs.
If you need to house routing equipment alongside connectivity, explore Exascale colocation. If you need exchange access rather than full internet reachability, compare remote peering. For an individual business site, review dedicated internet access.
Discuss a handoff at Exascale’s Telford site or an extension to an on-net address in Telford & Wrekin. Location, capacity and delivery requirements are checked for your quotation.
Discuss IP transit at Exascale’s Wolverhampton facility, with interconnection to IXMidlands, or an extension to an on-net address. Confirm the handoff and capacity required.
Discuss an IP transit handoff at Datum, Manchester. Provide the required port speed, committed bandwidth and cross-connect details so location and port availability can be checked.
Discuss an IP transit handoff at Lunar Digital, Manchester. Provide the required port speed, committed bandwidth and cross-connect details so location and port availability can be checked.
Discuss an IP transit handoff at Telehouse North, London. Provide the required port speed, committed bandwidth and cross-connect details so location and port availability can be checked.
Discuss an IP transit handoff at Telehouse West, London. Provide the required port speed, committed bandwidth and cross-connect details so location and port availability can be checked.
Discuss an IP transit handoff at Telehouse East, London. Provide the required port speed, committed bandwidth and cross-connect details so location and port availability can be checked.
Discuss an IP transit handoff at Telehouse North 2, London. Provide the required port speed, committed bandwidth and cross-connect details so location and port availability can be checked.
Discuss an IP transit handoff at Telehouse South, London. Provide the required port speed, committed bandwidth and cross-connect details so location and port availability can be checked.
Discuss an IP transit handoff at Redcentric, London. Provide the required port speed, committed bandwidth and cross-connect details so location and port availability can be checked.
Discuss an IP transit handoff at Nikhef, Amsterdam, NL. Provide the required port speed, committed bandwidth and cross-connect details so location and port availability can be checked.
Discuss an IP transit handoff at NTT FRA1, Frankfurt, DE. Provide the required port speed, committed bandwidth and cross-connect details so location and port availability can be checked.
Plan transit, peering and colocation together
Exascale network AS61049
Exascale AS61049 connects UK and European points of presence. Align your routing equipment, handoff, transit capacity and resilience requirements before selecting a delivery arrangement.
Our internet exchange guide explains how exchanges fit into the network. Read peering versus transit to understand why the two services can complement each other.
IP transit questions
What Is IP Transit and Who Needs It?
IP transit is a service that connects an organisation’s network to the wider internet. It is commonly used by internet…
View What Is IP Transit and Who Needs It?
Peering vs IP Transit: What’s the Difference?
Peering and IP transit both connect networks, but they serve different purposes. Understanding the distinction helps network operators plan reachability,…
View Peering vs IP Transit: What’s the Difference?What Is BGP and Why Does It Matter?
Border Gateway Protocol, or BGP, is used by networks to exchange routing information. It helps determine how traffic reaches destinations…
View What Is BGP and Why Does It Matter?BGP is available for networks managing their own routing, and static routing is also supported. Discuss your address resources, ASN and routing requirements so the delivery configuration can be agreed.
No. Port speed describes the interface capacity; committed bandwidth is the agreed service commitment. Your quotation identifies the committed rate and the treatment of traffic above it.
Agree the measurement method, committed rate and any burst or overage charges in your quotation. Do not assume every transit service uses the same billing method.
IP transit provides wider internet reachability through a provider. Peering exchanges traffic with participating networks and can complement transit. Our peering and IP transit guide explains the distinction.
Provide the delivery location, port speed, committed data rate, traffic profile, routing method, address resources, resilience requirements and preferred term. Include any cross-connect or extension requirements.
Request an IP transit quotation
Include your preferred point of presence, port speed, committed bandwidth, expected traffic profile, ASN or static-routing needs, contract term and cross-connect requirements.
We will check the delivery options and provide a quotation confirming capacity, charging basis, setup requirements and the applicable service terms.