Jinom Network Indonesia: PeeringDB fix list
AS138064 · peeringdb.com/net/20231
3 things to fix in Jinom Network Indonesia's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Jinom Network Indonesia's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in Jinom Network Indonesia's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.101.136.57 IPv6 2401:ee00:58:500::57 Speed Not published RS peer Not published
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.
-
Problem PeeringDB has The export has IPv4 address differs 103.175.82.3 103.175.82.35 103.122.64.34 - The entry with IPv4 103.175.82.3, IPv6 2403:8c40:a:a::3 isn't in the export: delete it if that connection is gone.
- The entry with IPv4 103.175.82.35, IPv6 2403:8c40:b:b::35 isn't in the export: delete it if that connection is gone.
- Add an entry: IPv4 103.122.64.34, IPv6 –, RS peer yes.
-
Problem PeeringDB has The export has Port speed differs 2 × 10G 40G + 10G - In the entry with IPv4 119.11.184.175: set Speed to 40000 (40G) (now 10000).
From ixreport.com/net/138064/: 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.