Blockinetic: PeeringDB fix list

AS13849 · peeringdb.com/net/29400

PeeringDB

2 things to fix in Blockinetic's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-10-08 20:58 UTC.

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

  1. Netherlands Frys-IX Fryslân, Netherlands · PeeringDB 3512From its IX-F export
    IPv4185.1.161.65
    IPv62001:7f8:10f::3619:320
    Speed10000 Mbps (10G)
    RS peerYes

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

Check these entries (1)

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

  1. Netherlands NSIX Amsterdam Amsterdam, Netherlands · PeeringDB 4589Not on its website members list
    IPv4193.192.12.30
    IPv62001:7f8:130::3619:1
    Speed1000 Mbps (1G)

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

From ixreport.com/net/13849/: 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.