Biznet Networks: PeeringDB fix list

AS17451 · peeringdb.com/net/1056

PeeringDB

2 things to fix in Biznet Networks's PeeringDB record, from what its exchanges publish: 1 to correct, 1 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.

Make the changes on Biznet Networks'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 IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    Port speed differs200G100G
    • In the entry with IPv4 123.108.8.194: set Speed to 100000 (100G) (now 200000).

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

Exchanges that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. Indonesia BIX Palembangghost Palembang, South Sumatra, Indonesia · PeeringDB 4851

    Only one outside network

    IPv4218.100.62.5
    IPv62001:de8:11:10:3:8060:1745:206
    Speed100000 Mbps (100G)

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