ixreport

Beeline_direct_net_1: PeeringDB fix list

AS8563

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

AS8563 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (1)

On the exchange's own member list, but not in Beeline_direct_net_1's PeeringDB record. Add one entry per connection with these values.

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

    2 connections, so 2 entries:

    IPv4178.18.227.86
    IPv62a03:5f80:4::227:86
    Speed50000 Mbps (50G)
    RS peerNo
    IPv4178.18.224.63
    IPv62a03:5f80:4::224:63
    Speed100000 Mbps (100G)
    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/8563/: 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.