Jembatan Data Pangrango: PeeringDB fix list
AS141071 · peeringdb.com/net/27891
3 things to fix in Jembatan Data Pangrango's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Jembatan Data Pangrango'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 (2)
On the exchange's own member list, but not in Jembatan Data Pangrango's PeeringDB record. Add one entry per connection with these values.
-
IPv4 – IPv6 2001:7f8:d0::2:270f:1 Speed Not published RS peer Yes -
IPv4 103.16.103.41 IPv6 2001:de8:12:100::103:41 Speed 10000 Mbps (10G) RS peer Yes
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 IPv6 address missing from PeeringDB none 2404:c8:0:a:0:14:1071:1 - In the entry with IPv4 119.11.185.37: set IPv6 to 2404:c8:0:a:0:14:1071:1 (now empty).
From ixreport.com/net/141071/: 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.