ixreport

HOSTLINE: PeeringDB fix list

AS198651 · peeringdb.com/net/10454

PeeringDB

2 things to fix in HOSTLINE's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on HOSTLINE'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. Lithuania BALT-IX Vilnius, Lithuania · PeeringDB 2005
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G

    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.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If HOSTLINE has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Finland FICIX 2 (Helsinki) Helsinki, Finland · PeeringDB 98Not on its website members list
    IPv4193.110.224.90
    IPv62001:7f8:7:b:0:2:778:5
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

From ixreport.com/net/198651/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.