EDGOO NETWORKS LEGACY: PeeringDB fix list

AS47787 · peeringdb.com/net/19503

PeeringDB

3 things to fix in EDGOO NETWORKS LEGACY's PeeringDB record, from what its exchanges publish: 2 to add, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on EDGOO NETWORKS LEGACY'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 (2)

On the exchange's own member list, but not in EDGOO NETWORKS LEGACY's PeeringDB record. Add one entry per connection with these values.

  1. India DE-CIX Mumbai Mumbai, India · PeeringDB 832From 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.

  2. Greece GR-IX::Athens Athens, Greece · PeeringDB 347From its IX-F export and website members list
    IPv4176.126.38.67
    IPv62001:7f8:6e::67
    Speed10000 Mbps (10G)
    RS peerYes

    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 EDGOO NETWORKS LEGACY has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Slovenia SIX SI Ljubljana, Slovenia · PeeringDB 319Not on its website members list
    IPv491.220.194.137
    IPv62001:7f8:46::4:7787
    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/47787/: 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.