ixreport

EMPEIRIA AI LTD: PeeringDB fix list

AS214565 · peeringdb.com/net/36704

PeeringDB

3 things to fix in EMPEIRIA AI LTD's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 22:13 UTC.

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

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:d0::3:4625:1
    SpeedNot published
    RS peerYes

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. United States DE-CIX Dallas Dallas, United States · PeeringDB 1249
    ProblemPeeringDB hasThe export has
    IPv4 address differs206.53.202.200206.53.202.197
    IPv6 address differs2001:504:61:0:3:4625:0:22001:504:61:0:3:4625:0:1
    • In the entry with IPv4 206.53.202.200: set IPv4 to 206.53.202.197 (now 206.53.202.200); set IPv6 to 2001:504:61:0:3:4625:0:1 (now 2001:504:61:0:3:4625:0:2).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If EMPEIRIA AI LTD 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 Frankfurt Frankfurt, Germany · PeeringDB 31Not on its IX-F export or website members list
    IPv480.81.196.121
    IPv62001:7f8::3:4625:0:2
    Speed200000 Mbps (200G)

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