ixreport

Precious netcom: PeeringDB fix list

AS133676 · peeringdb.com/net/9903

PeeringDB

One thing to fix in Precious netcom's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Precious netcom's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

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 Extreme IX Delhi Delhi, India · PeeringDB 1323
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 30G + 1G40G + 10G
    • In the entry with IPv6 2001:df2:1900:1::55: set Speed to 40000 (40G) (now 30000).
    • In the entry with IPv4 45.120.248.253: set Speed to 10000 (10G) (now 1000).
    • The entry with IPv4 45.120.248.55, IPv6 – isn't in the export: delete it if that connection is gone.

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