de Volksbank: PeeringDB fix list

AS57090 · peeringdb.com/net/16948

PeeringDB

One thing to fix in de Volksbank's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 UTC.

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

  1. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4193.239.118.243
    IPv62001:7f8:13::a505:7090:1
    SpeedNot published
    RS peerYes
    IPv4193.239.118.246
    IPv6–
    SpeedNot published
    RS peerNo

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

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