MAHABAL NET SERVICE PROVIDER: PeeringDB fix list

AS139543 · peeringdb.com/net/28154

PeeringDB

2 things to fix in MAHABAL NET SERVICE PROVIDER's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-10-08 20:58 UTC.

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

  1. India Extreme IX Hyderabad Hyderabad, India · PeeringDB 1785From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

    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 MAHABAL NET SERVICE PROVIDER 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 Mumbai Mumbai, India · PeeringDB 1627Not on its IX-F export
    IPv4103.77.108.190
    IPv62001:df2:1900:2::190
    Speed10000 Mbps (10G)

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