ixreport

IDNet

AS12496

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

4 things to fix in IDNet's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on IDNet'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 (2)

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

  1. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846From its IX-F export
    IPv4194.68.128.108
    IPv62001:7f8:d:fe::108
    Speed200 Mbps (200M)
    RS peerYes
  2. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70From its IX-F export
    IPv4194.68.123.108
    IPv62001:7f8:d:ff::108
    Speed200 Mbps (200M)
    RS peerYes

Correct these entries (2)

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 differs30G100G
    • In the entry with IPv4 195.66.224.181: set Speed to 100000 (100G) (now 30000).
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs30G100G
    • In the entry with IPv4 195.66.236.181: set Speed to 100000 (100G) (now 30000).

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, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where IDNet'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 100.4G across 5 exchanges.

United Kingdom LINX LON1 London, United Kingdom 195.66.224.181 2001:7f8:4::30d0:1 30G 11 routes Both Speed differs
United Kingdom LINX LON2 London, United Kingdom 195.66.236.181 2001:7f8:4:1::30d0:1 30G 12 routes Both Speed differs
United Kingdom LONAP London, United Kingdom 5.57.80.132
5.57.80.133
2001:7f8:17::30d0:1
2001:7f8:17::30d0:2
2 × 20G 24 routes Both
Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden 194.68.128.108 2001:7f8:d:fe::108 200M Down Not in PeeringDB
Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden 194.68.123.108 2001:7f8:d:ff::108 200M Yes Not in PeeringDB

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

These exchanges have a switch in a facility where IDNet lists itself in PeeringDB, but don't have IDNet 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 Digital Realty London LHR20; Telehouse - London (Docklands East)
Bulgaria NetIXSofia, Bulgaria 204 Digital Realty London LHR20; Telehouse - London (Docklands East)
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - London (Docklands East)
United Kingdom Kent Internet Exchange PointKent, United Kingdom 102 Digital Realty London LHR20
Facilities (2)

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

United Kingdom Digital Realty London LHR20London 3 of 6
United Kingdom Telehouse - London (Docklands East)London 3 of 6