ixreport

Pure IP

AS204264

Pure IP Limited

2Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
SelectivePeering policy
2Using the route servers
2To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with Pure IP? · Where should Pure IP peer next? · Compare Pure IP 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 Pure IP's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Pure IP'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 (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
    IPv6 address missing from PeeringDBnone2001:7f8:4::3:1de8:1
    Port speed differs1.024G10G
    • In the entry with IPv4 195.66.226.219: set IPv6 to 2001:7f8:4::3:1de8:1 (now empty); set Speed to 10000 (10G) (now 1024).
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4:1:0:3:1de8:1
    Port speed differs100M1G
    • In the entry with IPv4 195.66.238.219: set IPv6 to 2001:7f8:4:1:0:3:1de8:1 (now empty); set Speed to 1000 (1G) (now 100).

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 Pure IP'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 1.124G across 2 exchanges.

United Kingdom LINX LON1 London, United Kingdom 195.66.226.219 1.024G Up, 0 routes Both IPv6 not in PeeringDBSpeed differs
United Kingdom LINX LON2 London, United Kingdom 195.66.238.219 100M 1 routes Both IPv6 not in PeeringDBSpeed differs

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

These exchanges have a switch in a facility where Pure IP lists itself in PeeringDB, but don't have Pure IP 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 Equinix LD5 - London, Slough
United Kingdom LONAPLondon, United Kingdom 311 Equinix LD5 - London, Slough
Bulgaria NetIXSofia, Bulgaria 204 Equinix LD5 - London, Slough
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Equinix LD5 - London, Slough
United Kingdom Equinix LondonLondon, United Kingdom 53 Equinix LD5 - London, Slough
Facilities (2)

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

United Kingdom Equinix LD5 - London, SloughSlough 2 of 7
United Kingdom Redcentric London Data CentreLondon No exchange