ixreport

SGCC: PeeringDB fix list

AS147168 · peeringdb.com/net/30109

PeeringDB

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

Make the changes on SGCC'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. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    IPv4 address differs119.11.185.9 119.11.185.10 119.11.187.79119.11.185.9 119.11.185.10 119.11.185.255
    IPv6 address differs2404:c8:0:a:0:14:7168:32404:c8:0:a:0:14:7168:1 2404:c8:0:a:0:14:7168:2
    Port speed differs100G + 40G + 20G400G + 40G + 20G
    • In the entry with IPv4 119.11.185.10: set IPv6 to 2404:c8:0:a:0:14:7168:2 (now empty).
    • In the entry with IPv4 119.11.185.9: set IPv6 to 2404:c8:0:a:0:14:7168:1 (now empty).
    • The entry with IPv4 119.11.187.79, IPv6 2404:c8:0:a:0:14:7168:3 isn't in the export: delete it if that connection is gone.
    • Add an entry: IPv4 119.11.185.255, IPv6 –, speed 400000 (400G), RS peer yes.

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