National Internet Backbone India: PeeringDB fix list

AS9829 · peeringdb.com/net/15844

PeeringDB

4 things to fix in National Internet Backbone India's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on National Internet Backbone India'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 National Internet Backbone India's PeeringDB record. Add one entry per connection with these values.

  1. India DE-CIX Hyderabad Hyderabad, India · PeeringDB 4263From 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 (3)

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 Chennai Chennai, India · PeeringDB 2588
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 103.228.174.24: set Speed to 20000 (20G) (now 10000).
  2. India DE-CIX Delhi Delhi, India · PeeringDB 2587
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G + 2 × 200M
    • In the entry with IPv4 103.27.168.124: set Speed to 10000 (10G) (now 100000).
  3. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    Port speed differs100G80G
    • In the entry with IPv4 103.27.170.24: set Speed to 80000 (80G) (now 100000).

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