ixreport

Flexyz

AS202022 · Flexyz

Flexyz B.V.

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

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

Make the changes on Flexyz'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. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.239.116.101193.239.116.101 193.239.118.81
    IPv6 address missing from PeeringDB2001:7f8:13::a520:2022:22001:7f8:13::a520:2022:1 2001:7f8:13::a520:2022:2
    • Add an entry: IPv4 193.239.118.81, IPv6 2001:7f8:13::a520:2022:1, RS peer yes.

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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 Flexyz'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 11G across 2 exchanges.

Netherlands NDIX Enschede / Münster, Netherlands 193.108.98.169 2001:7f8:e::20:2022:1 1G Yes PeeringDB
Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 193.239.116.101 2001:7f8:13::a520:2022:2 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB

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

These exchanges have a switch in a facility where Flexyz lists itself in PeeringDB, but don't have Flexyz 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 (2)

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

Netherlands Iron Mountain Data Center - Amsterdam (AMS-1)Amsterdam 1 of 10
Netherlands QTS Groningen (GRO1)Groningen 1 of 2