ixreport

No One Internet

AS49375 · Leetline (www.leetline.co.uk)

No One Internet Ltd

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

Tools: Where can I peer with No One Internet? · Where should No One Internet peer next? · Compare No One Internet with another network

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

PeeringDB fix list Printable page · CSV

2 things to fix in No One Internet's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-11-19 12:40 UTC.

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

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs10G8G
    • In the entry with IPv4 195.66.224.36: set Speed to 8000 (8G) (now 10000).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If No One Internet has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321Not on its IX-F export or website members list
    IPv4195.66.236.36
    IPv62001:7f8:4:1::c0df:1
    Speed3000 Mbps (3G)

Exchanges over time

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

Map

Where No One Internet'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 13G across 2 exchanges.

United Kingdom LINX LON1 London, United Kingdom 195.66.224.36 2001:7f8:4::c0df:1 10G 18 routes Both Speed differs
United Kingdom LINX LON2 London, United Kingdom 195.66.236.36 2001:7f8:4:1::c0df:1 3G Yes PeeringDB only

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

These exchanges have a switch in a facility where No One Internet lists itself in PeeringDB, but don't have No One Internet 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.

United Kingdom LONAPLondon, United Kingdom 311 Digital Realty London LON1-3
Bulgaria NetIXSofia, Bulgaria 204 Digital Realty London LON1-3
United Kingdom RapidIX LON1London, United Kingdom 7 Digital Realty London LON1-3
Facilities (1)

The buildings No One Internet lists in PeeringDB, and how many of the exchanges in each it's on.

United Kingdom Digital Realty London LON1-3London 2 of 5