ixreport

IXPlay Route Servers

AS42229 · IXPlay-RS

IXPlay Global Peers

2Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Route ServerType
OpenPeering policy
1Using the route servers
1To fix in PeeringDB
4Facilities in PeeringDB

Tools: Where can I peer with IXPlay Route Servers? · Where should IXPlay Route Servers peer next? · Compare IXPlay Route Servers with another network

This network elsewhere: its registry history on RIR Tracker

PeeringDB fix list Printable page · CSV

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

Make the changes on IXPlay Route Servers'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 IXPlay Route Servers's PeeringDB record. Add one entry per connection with these values.

  1. Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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 IXPlay Route Servers'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 20G, at the 1 of 2 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland Not in PeeringDB
Spain IXPlay Global Peers Madrid, Spain 185.1.90.1
185.1.90.2
2001:7f8:b2:0:724:4:2229:1
2001:7f8:b2:0:724:4:2229:2
2 × 10G Yes PeeringDB

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

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

Facilities (4)

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

Spain Digital Realty Madrid MAD1-2Madrid 2 of 8
Spain Barcelona Cable Landing StationSant Adrià de Besòs 1 of 5
Spain Templus DC Madrid MAD03Madrid 1 of 1
Spain Templus DC Málaga MAL01Málaga 1 of 1