ixreport

ixupdates.abater.io: PeeringDB fix list

AS65111

3 things to fix in ixupdates.abater.io's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-10-08 18:53 UTC.

AS65111 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (3)

On the exchange's own member list, but not in ixupdates.abater.io's PeeringDB record. Add one entry per connection with these values.

  1. India Extreme IX Chennai Chennai, India · PeeringDB 1786From its IX-F export
    IPv445.120.251.92
    IPv62001:df2:1900:3::92
    Speed100 Mbps (100M)
    RS peerYes

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

  2. India Extreme IX Delhi Delhi, India · PeeringDB 1323From its IX-F export
    IPv445.120.248.192
    IPv62001:df2:1900:1::192
    Speed100 Mbps (100M)
    RS peerYes

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

  3. India Extreme IX Mumbai Mumbai, India · PeeringDB 1627From its IX-F export
    IPv4103.77.109.16
    IPv62001:df2:1900:2::1016
    Speed100 Mbps (100M)
    RS peerYes

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