INTEK-M: PeeringDB fix list

AS43865 · peeringdb.com/net/34877

PeeringDB

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

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

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    5 connections, so 5 entries:

    IPv4178.18.224.126
    IPv6–
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.224.132
    IPv6–
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.224.134
    IPv6–
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.224.135
    IPv6–
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.224.137
    IPv6–
    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.

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