ixreport

TecnoWeb: PeeringDB fix list

AS64114 · peeringdb.com/net/18680

PeeringDB

5 things to fix in TecnoWeb's PeeringDB record, from what its exchanges publish: 1 to add, 4 to check. As of 2026-10-08 18:53 UTC.

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

  1. Egypt PyramIX Cairo, Egypt · PeeringDB 3302From its website members list
    IPv4–
    IPv62a0e:46c4:102::641:14:1
    SpeedNot published
    RS peerNot published

Check these entries (4)

In PeeringDB, but on none of the exchange's own lists. If TecnoWeb 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 Dusseldorf Düsseldorf, Germany · PeeringDB 1214Not on its IX-F export or website members list
    IPv4185.1.170.239
    IPv62001:7f8:9e::fa72:0:1
    Speed10000 Mbps (10G)
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31Not on its IX-F export or website members list
    IPv480.81.193.49
    IPv62001:7f8::fa72:0:1
    Speed10000 Mbps (10G)
  3. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74Not on its IX-F export or website members list
    IPv4185.1.210.101
    IPv62001:7f8:3d::fa72:0:1
    Speed10000 Mbps (10G)
  4. Germany DE-CIX Munich Munich, Germany · PeeringDB 248Not on its IX-F export or website members list
    IPv4185.1.208.236
    IPv62001:7f8:44::fa72:0:1
    Speed10000 Mbps (10G)

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