iForte Solusi Infotek - eXchange: PeeringDB fix list
AS137367 · peeringdb.com/net/17980
3 things to fix in iForte Solusi Infotek - eXchange's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on iForte Solusi Infotek - eXchange'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 iForte Solusi Infotek - eXchange's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.16.102.161 IPv6 2001:de8:12:100::161 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 Port speed differs 10G 3G - In the entry with IPv4 195.66.226.124: set Speed to 3000 (3G) (now 10000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If iForte Solusi Infotek - eXchange has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 210.171.225.158 IPv6 2001:de8:8::13:7367:1 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/137367/: 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.