ixreport

NGENIX: PeeringDB fix list

AS34879 · peeringdb.com/net/5453

PeeringDB

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

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

  1. Kyrgyzstan KG-IX Bishkek Bishkek, Kyrgyzstan · PeeringDB 2145From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (3)

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
    IPv6 address missing from PeeringDBnone2a03:5f80:4::224:131 2a03:5f80:4::224:223
    • In the entry with IPv4 178.18.224.131: set IPv6 to 2a03:5f80:4::224:131 (now empty).
    • In the entry with IPv4 178.18.224.223: set IPv6 to 2a03:5f80:4::224:223 (now empty).

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

  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:20:101::208:37 2001:7f8:20:101::208:74 2001:7f8:20:101::209:91
    • In the entry with IPv4 195.208.208.37: set IPv6 to 2001:7f8:20:101::208:37 (now empty).
    • In the entry with IPv4 195.208.208.74: set IPv6 to 2001:7f8:20:101::208:74 (now empty).
    • In the entry with IPv4 195.208.209.91: set IPv6 to 2001:7f8:20:101::209:91 (now empty).

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

  3. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:20:201::100:48 2001:7f8:20:202::102:48
    • In the entry with IPv4 194.226.100.48: set IPv6 to 2001:7f8:20:201::100:48 (now empty).
    • In the entry with IPv4 194.226.102.48: set IPv6 to 2001:7f8:20:202::102:48 (now empty).

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