Extreme IX Fast Peering: PeeringDB fix list

AS135814 · peeringdb.com/net/12573

PeeringDB

3 things to fix in Extreme IX Fast Peering's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.

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

  1. India Extreme IX Pune Pune, India · PeeringDB 4805From its IX-F export
    IPv4123.253.159.100
    IPv62001:df2:1900:6::100
    Speed200000 Mbps (200G)
    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. ProblemPeeringDB hasThe export has
    Port speed differs400G400G + 10G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Check these entries (1)

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

  1. India Extreme IX Hyderabad Hyderabad, India · PeeringDB 1785Not on its IX-F export
    IPv4103.77.110.222
    IPv62001:df2:1900:4::222
    Speed10000 Mbps (10G)

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