Our Partners
Multi-homed global IPv4/v6 carriers:
Peering exchanges for low-latency EU routes reaching 30%+ of IPv4 and 100% of IPv6:
Available PoPs
We supply IP transit in all major London data centres, including:
London Docklands: Telehouse North, Telehouse East, Telehouse West, Telecity Sovereign House, Harbour Exchange 6&7, Harbour Exchange 8&9, Meridian Gate (Memaco House), Global Switch London 1, Global Switch London 2, Telstra London Hosting Centre, City Reach Tutis Point
London City: London Bridge, Interxion LON1/LON2, City LifeLine, Telehouse Metro, Level(3) Goswell Road
Greater London: Greenwich, Croydon, West Byfleet, Equinix LD4/LD5 (Slough)
Global Transit
- Access the entire IPv4/v6 global Internet
- Multi-homed for carrier/site resilience
- 2 of the top 3 Tier 1 upstreams: NTT and TeliaSonera IC
- Peered routes for lowest latency
100M from £4/Mbps per month
Partial Transit
- For BGP sessions only
- Supplies 30-35% of all global routes
- Low-latency connectivity via major peering exchanges in UK and Europe
- Highly cost-effective for local traffic
100M from £1/Mbps per month
Request Quote
| What is IP transit? | How is it delivered? |
|---|---|
| A high-bandwidth symmetrical service used to connect your data centre equipment to the Internet. | In any of our 15 points of presence (PoPs), we run a copper or fibre cross-connect cable to you. |
| How is transit charged? | Does the service require BGP? |
| Using 95th percentile committed data rate over either 100Mbps or 1Gbps burstable ports. | No. If you do not have your own AS network, we will assign you static IPs on our address space. |
Service Levels
We operate our own multi-homed BGP network (AS51945) based on a 10Gbps MPLS core, two diverse routing sites with independent hardware, dual global upstreams and a substantial complement of peered traffic. Combined with continual monitoring, this ensures we maintain the highest possible uptime: 100% most months and 99.99%+ annually, as shown by these independent statistics from Pingdom which include all scheduled maintenance windows and "natural" reconvergence events (e.g. peer drops and upstream maintenance).
In addition to high uptime, we strive to optimise traffic to use best path not lowest cost routing, which gives these typical low latency round trip times (RTTs) to major landing sites outside London:
| UK: | Scotland | <10ms | Ireland | <12ms |
|---|---|---|---|---|
| Europe Landing: | Netherlands | <10ms | France | <14ms |
| Rest of Europe: | Western Europe | 20-30ms | Eastern Europe | 25-40ms |
| USA: | East Coast | 70-90ms | West Coast | 120-160ms |
| Americas: | Central America | 100-140ms | South America | 170-220ms |
| Asia: | Singapore | 200ms | Japan | 240ms |
The table shows round-trip-times (RTTs), measured as time between an ICMP "ping" request being sent and the reply packet received. For uni-directional protocols like UDP and VoIP, the time delay between sending data and the recipient receiving the packet will be half of that shown above. If your applications are latency sensitive to a specific remote location, please contact us and we'll be happy to assist with specific ping tests and traceroutes from our network core.
Come join us on:
and read our blog