ixreport

Devout BV: PeeringDB fix list

AS216471 · peeringdb.com/net/35489

PeeringDB

One thing to fix in Devout BV's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 18:53 UTC.

Make the changes on Devout BV'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 Devout BV'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
    IPv4193.239.119.71
    IPv62001:7f8:13::a521:6471:1
    SpeedNot published
    RS peerYes

    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/216471/: 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.