ixreport

Extreme IX Route Servers: PeeringDB fix list

AS49378 · peeringdb.com/net/14583

PeeringDB

5 things to fix in Extreme IX Route Servers's PeeringDB record, from what its exchanges publish: 1 to add, 4 to correct. As of 2026-10-08 21:56 UTC.

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

  1. India Extreme IX Pune Pune, India · PeeringDB 4805From its IX-F export

    2 connections, so 2 entries:

    IPv4123.253.159.200
    IPv62001:df2:1900:6::200
    Speed20000 Mbps (20G)
    RS peerNo
    IPv4123.253.159.240
    IPv62001:df2:1900:6::240
    Speed20000 Mbps (20G)
    RS peerNo

Correct these entries (4)

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 differs2 × 10G10G

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

  2. ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G1G
    • In the entry with IPv4 45.120.248.200: set Speed to 1000 (1G) (now 10000).
    • In the entry with IPv4 45.120.248.240: 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.

  3. ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G

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

  4. ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G

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