SYSTEM 3 NET TECHNOLOGIES: PeeringDB fix list

AS45189 · peeringdb.com/net/42272

PeeringDB

One thing to fix in SYSTEM 3 NET TECHNOLOGIES's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on SYSTEM 3 NET TECHNOLOGIES'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 DE-CIX Delhi Delhi, India · PeeringDB 2587
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2400:d180:67::91
    Port speed differs1G10G + 1G
    • In the entry with IPv4 103.27.168.91: set IPv6 to 2400:d180:67::91 (now empty).

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