ixreport

AVS ISP: PeeringDB fix list

AS210464 · peeringdb.com/net/28594

PeeringDB

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

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

Correct these entries (2)

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. Romania DSIX Bucharest, Romania · PeeringDB 3477
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 185.0.0.13: set Speed to 1000 (1G) (now 10000).

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

  2. United States F4IX MCI Kansas City, United States · PeeringDB 4378
    ProblemPeeringDB hasThe export has
    Port speed differs10G100M
    • In the entry with IPv4 149.112.75.34: set Speed to 100 (100M) (now 10000).

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

Check these entries (1)

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

  1. Netherlands NSIX Amsterdam Amsterdam, Netherlands · PeeringDB 4589Not on its website members list
    IPv4193.192.12.29
    IPv62001:7f8:130::3:3620:1
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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