ixreport

JKT-IX Route Servers

AS137295 · JKT-IX Route Server

NTT DATA's Global Data Centers division

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

Tools: Where can I peer with JKT-IX Route Servers? · Where should JKT-IX Route Servers peer next? · Compare JKT-IX Route Servers with another network

This network elsewhere: the registry history of AS137285-AS137384, the block AS137295 is in, on RIR Tracker

PeeringDB fix list Printable page · CSV

One thing to fix in JKT-IX Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on JKT-IX Route Servers'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 JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB2404:c8:0:a:0:13:7295:3 is AS140016 TRIK MEDIA DATA2404:c8:0:a:0:13:7295:3
    IPv6 address in PeeringDB, not in the export2404:c8:0:a:0:13:7295:1 2404:c8:0:a:0:13:7295:22404:c8:0:a:0:13:7295:2 2404:c8:0:a:0:13:7295:3
    Port speed differs3 × 1G10G + 2 × 1G

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    • In the entry with IPv4 119.11.184.101: set IPv6 to (empty) (now 2404:c8:0:a:0:13:7295:1).
    • In the entry with IPv4 119.11.184.102: set Speed to 10000 (10G) (now 1000).
    • In the entry with IPv4 119.11.185.222: set Speed to 10000 (10G) (now 1000).

Exchanges over time

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

Map

Where JKT-IX Route Servers'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 4G across 2 exchanges.

Indonesia JKT-IX Jakarta, Indonesia 119.11.184.101
119.11.184.102
119.11.185.222
2404:c8:0:a:0:13:7295:1
2404:c8:0:a:0:13:7295:2
3 × 1G Yes Both Address takenIPv6 not in exportSpeed differs
Indonesia JKT-IX Surabaya Surabaya, Indonesia 119.11.193.101 2404:c8:0:c:0:13:7295:1 1G PeeringDB

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

These exchanges have a switch in a facility where JKT-IX Route Servers lists itself in PeeringDB, but don't have JKT-IX Route Servers 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 (2)

The buildings JKT-IX Route Servers lists in PeeringDB, and how many of the exchanges in each it's on.

Indonesia NTT Jakarta 2 Data Center (JKT2)Jakarta 1 of 12
Indonesia NTT Jakarta 3 Data Center (JKT3)Jakarta 1 of 2