ixreport

JENTRE NET

AS153100 · JENTRE NET

PT Jentre Media Nusa

7Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
7Using the route servers
3To fix in PeeringDB
2Facilities in PeeringDB

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

This network elsewhere: the registry history of AS153059-AS153158, the block AS153100 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in JENTRE NET's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-11-19 12:40 UTC.

Make the changes on JENTRE NET'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 (2)

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 DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df6:480:0:2:560c:0:1
    • In the entry with IPv4 103.162.254.146: set IPv6 to 2001:df6:480:0:2:560c:0:1 (now empty).
  2. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::3a1
    • In the entry with IPv4 123.108.11.145: set IPv6 to 2001:7fa:2:5::3a1 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If JENTRE NET has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Indonesia CXC Jakarta Jakarta, Indonesia · PeeringDB 2737Not on its website members list
    IPv4103.225.172.37
    IPv62400:9c80:0:173:0:1531::
    Speed1000 Mbps (1G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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 JENTRE NET'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 34G across 7 exchanges.

Indonesia AIX Tapos, Depok, Indonesia 43.254.83.58 1G Yes Both
Indonesia CXC Jakarta Jakarta, Indonesia 103.225.172.37 2400:9c80:0:173:0:1531:: 1G Yes PeeringDB only
Singapore DE-CIX ASEAN Singapore, Singapore 103.162.254.146 10G 1 routes Both IPv6 not in PeeringDB
Indonesia DE-CIX Jakarta Jakarta, Indonesia 49.213.56.75 2001:df5:7880:0:2:560c:0:1 10G 1 routes Both
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.11.145 1G Yes Both IPv6 not in PeeringDB
Indonesia JKT-IX Jakarta, Indonesia 119.11.184.224 1G Yes Both
Indonesia OpenIXP / NiCE Indonesia, Indonesia 43.252.147.122 10G Yes PeeringDB

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

These exchanges have a switch in a facility where JENTRE NET lists itself in PeeringDB, but don't have JENTRE NET 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.

Bulgaria NetIXSofia, Bulgaria 204 Datacenter APJII-Cyber
Indonesia BIX JakartaJakarta, Indonesia 180 Datacenter APJII-Cyber; IDC 3D
Indonesia ILIXSurabaya, Indonesia 122 Datacenter APJII-Cyber
Indonesia OMNIIX INDONESIABatam, Jakarta, Indonesia 111 IDC 3D
Indonesia Transhybrid IX NetworkJakarta, Indonesia 63 Datacenter APJII-Cyber; IDC 3D
Indonesia CENTRO-IXPekanbaru - Jakarta, Indonesia 39 Datacenter APJII-Cyber
Indonesia CNI-IXJakarta, Indonesia 18 Datacenter APJII-Cyber; IDC 3D
Indonesia Metta-IXJakarta, Indonesia 16 Datacenter APJII-Cyber
Indonesia GPMIXLampung Timur, Indonesia 13 Datacenter APJII-Cyber
Indonesia JDXJakarta, Indonesia 13 Datacenter APJII-Cyber; IDC 3D
Indonesia Swin ExchangeDepok, Indonesia 13 IDC 3D
Indonesia BatamIX JakartaJakarta, Indonesia 7 Datacenter APJII-Cyber; IDC 3D
Indonesia IFORTE XchangeJakarta, Indonesia 7 IDC 3D
Indonesia Super Internet eXchange (SIX)Bogor, Indonesia 4 Datacenter APJII-Cyber
Indonesia ABS-IXJAKARTA, Indonesia 3 Datacenter APJII-Cyber
Facilities (2)

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

Indonesia Datacenter APJII-CyberJakarta Selatan 5 of 17
Indonesia IDC 3DJakarta Selatan 4 of 12