ixreport

Quickline Communications

AS57099

Quickline Communications Ltd

5Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
4Using the route servers
1To fix in PeeringDB
5Facilities in PeeringDB

Tools: Where can I peer with Quickline Communications? · Where should Quickline Communications peer next? · Compare Quickline Communications with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Quickline Communications's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on Quickline Communications's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in Quickline Communications's PeeringDB record. Add one entry per connection with these values.

  1. United Kingdom IXLeeds Leeds / Western Yorkshire, United Kingdom · PeeringDB 435From its IX-F export and website members list
    IPv491.217.231.28
    IPv62001:7f8:67::df0b:1
    SpeedNot published
    RS peerNot published

Exchanges over time

0246Oct 3, 2026Nov 19, 20265
Show as a table
DateExchanges
Nov 19, 20265
Nov 18, 20265
Nov 17, 20265
Nov 16, 20265
Nov 15, 20265
Nov 14, 20265
Nov 13, 20265
Nov 12, 20265
Nov 11, 20265
Nov 10, 20265
Nov 9, 20265
Nov 8, 20265
Nov 7, 20265
Nov 6, 20265
Nov 5, 20265
Nov 4, 20265
Nov 3, 20265
Nov 2, 20265
Nov 1, 20265
Oct 31, 20265
Oct 30, 20265
Oct 29, 20265
Oct 28, 20265
Oct 27, 20265
Oct 26, 20265
Oct 25, 20265
Oct 24, 20265
Oct 23, 20265
Oct 22, 20265
Oct 21, 20265
Oct 20, 20265
Oct 19, 20265
Oct 18, 20265
Oct 17, 20265
Oct 16, 20265
Oct 15, 20265
Oct 14, 20265
Oct 13, 20265
Oct 12, 20265
Oct 11, 20265
Oct 10, 20265
Oct 9, 20265
Oct 8, 20265
Oct 7, 20265
Oct 6, 20265
Oct 5, 20265
Oct 4, 20265
Oct 3, 20265

Map

Where Quickline Communications's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 400G, at the 4 of 5 exchanges with a speed in PeeringDB or the exchange's IX-F export.

United Kingdom IXLeeds Leeds / Western Yorkshire, United Kingdom 91.217.231.28 2001:7f8:67::df0b:1 Not in PeeringDB
United Kingdom LINX LON1 London, United Kingdom 195.66.226.178 2001:7f8:4::df0b:1 100G 16 routes Both
United Kingdom LINX LON2 London, United Kingdom 195.66.238.178 2001:7f8:4:1::df0b:1 100G 16 routes Both
United Kingdom LINX Manchester Manchester, United Kingdom 195.66.244.70 2001:7f8:4:2::df0b:1 100G 15 routes Both
United Kingdom LONAP London, United Kingdom 5.57.81.118 2001:7f8:17::df0b:1 100G 16 routes Both

Exchanges in its buildings that it isn't on (2)

These exchanges have a switch in a facility where Quickline Communications lists itself in PeeringDB, but don't have Quickline Communications as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 Telehouse - London (Docklands North Two)
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - London (Docklands North Two)
Facilities (5)

The buildings Quickline Communications lists in PeeringDB, and how many of the exchanges in each it's on.

United Kingdom Telehouse - London (Docklands North Two)London 3 of 5
United Kingdom Teledata Manchester - Delta HouseManchester 1 of 1
United Kingdom aql DC3Leeds No exchange
United Kingdom aql DC5Leeds No exchange
United Kingdom Templus DC Leeds LEE01Leeds No exchange