Sathya Web Services: PeeringDB fix list
AS139484 · peeringdb.com/net/28299
One thing to fix in Sathya Web Services's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Sathya Web Services'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.
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 103.228.174.22 103.228.174.25 103.228.174.22 IPv6 address in PeeringDB, not in the export 2400:d180:68::22 2400:d180:68::25 2400:d180:68::22 Port speed differs 2 × 10G 2 × 10G + 2 × 5G + 3G - The entry with IPv4 103.228.174.25, IPv6 2400:d180:68::25 isn't in the export: delete it if that connection is gone.
From ixreport.com/net/139484/: 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.