ixreport

Royal Network Technology: PeeringDB fix list

AS133731 · peeringdb.com/net/14694

PeeringDB

3 things to fix in Royal Network Technology's PeeringDB record, from what its exchanges publish: 3 to check. As of 2026-10-08 18:53 UTC.

Make the changes on Royal Network Technology's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Check these entries (3)

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

  1. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74Not on its IX-F export or website members list
    IPv4185.1.210.68
    IPv62001:7f8:3d:0:2:a63:0:1
    Speed100 Mbps (100M)
  2. Germany DE-CIX Munich Munich, Germany · PeeringDB 248Not on its IX-F export or website members list
    IPv4185.1.208.56
    IPv62001:7f8:44:0:2:a63:0:1
    Speed100 Mbps (100M)
  3. Hong Kong HKIX Hong Kong, Hong Kong · PeeringDB 42Not on its IX-F export
    IPv4123.255.91.85
    IPv62001:7fa:0:1::ca28:a155
    Speed10000 Mbps (10G)

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