ixreport

FAB FIVE NETWORK PRIVATE LIMITED: PeeringDB fix list

AS151690 · peeringdb.com/net/34858

PeeringDB

5 things to fix in FAB FIVE NETWORK PRIVATE LIMITED's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on FAB FIVE NETWORK PRIVATE LIMITED'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 FAB FIVE NETWORK PRIVATE LIMITED's PeeringDB record. Add one entry per connection with these values.

  1. India DE-CIX Chennai Chennai, India · PeeringDB 2588From 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. India Extreme IX Pune Pune, India · PeeringDB 4805From 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.

Correct these entries (2)

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. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2401:7500:fff6::97
    • In the entry with IPv4 103.27.170.97: set IPv6 to 2401:7500:fff6::97 (now empty).
  2. India Extreme IX Mumbai Mumbai, India · PeeringDB 1627
    ProblemPeeringDB hasThe export has
    Port speed differs100G + 10G100G + 2 × 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 FAB FIVE NETWORK PRIVATE LIMITED 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 Chennai Chennai, India · PeeringDB 1786Not on its IX-F export
    IPv445.120.251.62
    IPv62001:df2:1900:3::62
    Speed10000 Mbps (10G)

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