ixreport

Jalabyte

AS139205

PT Jala Informatika Nusantara

7Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
6Using the route servers
1To fix in PeeringDB
4Facilities in PeeringDB

Tools: Where can I peer with Jalabyte? · Where should Jalabyte peer next? · Compare Jalabyte with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Jalabyte's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Jalabyte'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 differs400G10G
    • In the entry with IPv4 123.108.11.253: set Speed to 10000 (10G) (now 400000).

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

Exchanges over time

02468Oct 3, 2026Nov 19, 20267
Show as a table
DateExchanges
Nov 19, 20267
Nov 18, 20267
Nov 17, 20267
Nov 16, 20267
Nov 15, 20267
Nov 14, 20267
Nov 13, 20267
Nov 12, 20267
Nov 11, 20267
Nov 10, 20267
Nov 9, 20267
Nov 8, 20267
Nov 7, 20267
Nov 6, 20267
Nov 5, 20267
Nov 4, 20267
Nov 3, 20267
Nov 2, 20267
Nov 1, 20267
Oct 31, 20267
Oct 30, 20267
Oct 29, 20267
Oct 28, 20267
Oct 27, 20267
Oct 26, 20267
Oct 25, 20267
Oct 24, 20267
Oct 23, 20267
Oct 22, 20267
Oct 21, 20267
Oct 20, 20267
Oct 19, 20267
Oct 18, 20267
Oct 17, 20267
Oct 16, 20267
Oct 15, 20267
Oct 14, 20267
Oct 13, 20267
Oct 12, 20267
Oct 11, 20267
Oct 10, 20267
Oct 9, 20267
Oct 8, 20267
Oct 7, 20267
Oct 6, 20267
Oct 5, 20267
Oct 4, 20267
Oct 3, 20267

Map

Where Jalabyte's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 424G across 7 exchanges.

Indonesia AIX Tapos, Depok, Indonesia 43.254.83.122 2401:91e0:31::139:205:1 1G Yes Both
Indonesia EdgeNXT Jakarta, Indonesia 103.61.232.139 2001:df1:d440:1::8b 1G Yes PeeringDB
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.11.253 2001:7fa:2:5::40d 400G Yes Both Speed differs
Indonesia ILIX Surabaya, Indonesia 157.10.16.57 2404:2f80:206::57 10G Yes PeeringDB
Indonesia JKT-IX Jakarta, Indonesia 119.11.187.97 2404:c8:0:a:0:13:9205:1 1G Yes Both
Indonesia OMNIIX INDONESIA Batam, Jakarta, Indonesia 43.255.59.82 2401:a320::66 10G Yes Both
Indonesia OpenIXP / NiCE Indonesia, Indonesia 43.252.147.135 1G PeeringDB

Exchanges in its buildings that it isn't on (16)

These exchanges have a switch in a facility where Jalabyte lists itself in PeeringDB, but don't have Jalabyte as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (4)

The buildings Jalabyte lists in PeeringDB, and how many of the exchanges in each it's on.

Indonesia Datacenter APJII-CyberJakarta Selatan 3 of 17
Indonesia IDC 3DJakarta Selatan 3 of 12
Indonesia NTT Jakarta 2 Data Center (JKT2)Jakarta 5 of 12
Indonesia ProDCJakarta Selatan 1 of 2