Jala Lintas Media AS133840: PeeringDB fix list

AS133840 · peeringdb.com/net/13404

PeeringDB

3 things to fix in Jala Lintas Media AS133840's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.

Make the changes on Jala Lintas Media AS133840'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 Jala Lintas Media AS133840's PeeringDB record. Add one entry per connection with these values.

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 103.16.102.231: set Speed to 20000 (20G) (now 10000).

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. Only the operator's own networks

    IPv4202.145.15.3
    IPv62402:69c0:77:0:1:3:3840:1
    Speed10000 Mbps (10G)

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