Starnet: PeeringDB fix list

AS55699 · peeringdb.com/net/10136

PeeringDB

2 things to fix in Starnet's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Starnet'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 (2)

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 IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 123.108.8.76: set Speed to 10000 (10G) (now 100000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    IPv6 address differs2404:c8:0:a:0:5:5699:12404:c8:0:a:0:5:5699:2
    • In the entry with IPv4 119.11.185.62: set IPv6 to 2404:c8:0:a:0:5:5699:2 (now 2404:c8:0:a:0:5:5699:1).

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