ixreport

FPLNET

AS218255 · FinnPL

Finn Paul Lippok

WebsitePeeringDB Follow changes
2Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Non-ProfitType
OpenPeering policy
2Using the route servers
1To fix in PeeringDB
0Facilities in PeeringDB

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

Make the changes on FPLNET'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 INTERIX Amsterdam, Netherlands · PeeringDB 3990
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.1.185.17
    • In the entry with IPv6 2001:7f8:134::10e: set IPv4 to 185.1.185.17 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

012Oct 31, 2026Nov 12, 20262

Collecting since Oct 31, 2026: one point a day, so this fills in as the days go by.

Show as a table
DateExchanges
Nov 12, 20262
Nov 11, 20262
Nov 10, 20262
Nov 9, 20261
Nov 8, 20261
Nov 7, 20261
Nov 6, 20261
Nov 5, 20261
Nov 4, 20261
Nov 3, 20261
Nov 2, 20261
Nov 1, 20261
Oct 31, 20261

In the last 30 days FPLNET joined 2 exchanges and left 0. Growing networks

Joined

Map

Where FPLNET'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 101G across 2 exchanges.
Netherlands INTERIX Amsterdam, Netherlands 2001:7f8:134::10e 100G 3 routes Both IPv4 not in PeeringDB
Germany LOCIX DUSSELDORF Dusseldorf, Germany 2a0c:b641:701:0:a5:21:8255:1 1G Yes PeeringDB

FPLNET lists no facilities in PeeringDB.

Recent changes Search them

  • Nov 10, 2026 [PDB] AS218255 FPLNET now in PeeringDB at INTERIX
  • Nov 10, 2026 [IXF] AS218255 FPLNET added to INTERIX
  • Oct 31, 2026 [PDB] AS218255 FPLNET added to LOCIX DUSSELDORF