Multi-homed global IPv4/v6 carriers:
Peering exchanges for low-latency EU routes reaching 30%+ of IPv4 and 100% of IPv6:
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
100M from £3/Mbps per month
100M from £1/Mbps per month
|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.|
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:
|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|
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.
"I'd like to thank ConnetU for always responding promptly to our managed server requirements. Reliability is key to our business and has consistently met our high expectations. All in all, an excellent hosting service."
Thank you for completing the technical outline of your requirement; this is now ready to be submitted to a sales advisor by completing the form below. You can leave the Supplementary details empty unless you need to supply additional information or variations not already captured. We aim to return all enquiries within one business day:
As our solutions can all be tailored to specific requirements, a pre-sales advisor will need to contact you to discuss a proposal. Please supply your contact information and an outline of your enquiry below and we will aim to return your enquiry within one business day: