ixreport

DA International Group Ltd.: PeeringDB fix list

AS203380 · peeringdb.com/net/26803

PeeringDB

2 things to fix in DA International Group Ltd.'s PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.

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

  1. Bulgaria TurkIX Sofia Sofia, Bulgaria · PeeringDB 4186From its IX-F export and website members list
    IPv4194.42.47.27
    IPv62001:7f8:161::27
    Speed100000 Mbps (100G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.237.0178.18.237.0 178.18.237.104
    IPv6 address missing from PeeringDB2a03:5f80:4:2::237:02a03:5f80:4:2::237:0 2a03:5f80:4:2::237:104
    • Add an entry: IPv4 178.18.237.104, IPv6 2a03:5f80:4:2::237:104, speed 100000 (100G), RS peer yes.

    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/203380/: 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.