JKT-IX Route Servers
AS137295 · JKT-IX Route Server
NTT DATA's Global Data Centers division
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.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 2404:c8:0:a:0:13:7295:3 is AS140016 TRIK MEDIA DATA 2404:c8:0:a:0:13:7295:3 IPv6 address in PeeringDB, not in the export 2404:c8:0:a:0:13:7295:1 2404:c8:0:a:0:13:7295:2 2404:c8:0:a:0:13:7295:2 2404:c8:0:a:0:13:7295:3 Port speed differs 3 × 1G 10G + 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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 2 |
| Nov 18, 2026 | 2 |
| Nov 17, 2026 | 2 |
| Nov 16, 2026 | 2 |
| Nov 15, 2026 | 2 |
| Nov 14, 2026 | 2 |
| Nov 13, 2026 | 2 |
| Nov 12, 2026 | 2 |
| Nov 11, 2026 | 2 |
| Nov 10, 2026 | 2 |
| Nov 9, 2026 | 2 |
| Nov 8, 2026 | 2 |
| Nov 7, 2026 | 2 |
| Nov 6, 2026 | 2 |
| Nov 5, 2026 | 2 |
| Nov 4, 2026 | 2 |
| Nov 3, 2026 | 2 |
| Nov 2, 2026 | 2 |
| Nov 1, 2026 | 2 |
| Oct 31, 2026 | 2 |
| Oct 30, 2026 | 2 |
| Oct 29, 2026 | 2 |
| Oct 28, 2026 | 2 |
| Oct 27, 2026 | 2 |
| Oct 26, 2026 | 2 |
| Oct 25, 2026 | 2 |
| Oct 24, 2026 | 2 |
| Oct 23, 2026 | 2 |
| Oct 22, 2026 | 2 |
| Oct 21, 2026 | 2 |
| Oct 20, 2026 | 2 |
| Oct 19, 2026 | 2 |
| Oct 18, 2026 | 2 |
| Oct 17, 2026 | 2 |
| Oct 16, 2026 | 2 |
| Oct 15, 2026 | 2 |
| Oct 14, 2026 | 2 |
| Oct 13, 2026 | 2 |
| Oct 12, 2026 | 2 |
| Oct 11, 2026 | 2 |
| Oct 10, 2026 | 2 |
| Oct 9, 2026 | 2 |
| Oct 8, 2026 | 2 |
| Oct 7, 2026 | 2 |
| Oct 6, 2026 | 2 |
| Oct 5, 2026 | 2 |
| Oct 4, 2026 | 2 |
| Oct 3, 2026 | 2 |
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.
| JKT-IX Jakarta, Indonesia | 3 × 1G | Both Address takenIPv6 not in exportSpeed differs | |
| JKT-IX Surabaya Surabaya, Indonesia | 1G | PeeringDB |
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.
| IIX-JakartaJakarta, Indonesia | 978 | |
| AIXTapos, Depok, Indonesia | 343 | |
| CXC JakartaJakarta, Indonesia | 201 | |
| DE-CIX JakartaJakarta, Indonesia | 177 | |
| ILIXSurabaya, Indonesia | 122 | |
| OMNIIX INDONESIABatam, Jakarta, Indonesia | 111 | |
| Transhybrid IX NetworkJakarta, Indonesia | 63 | |
| CENTRO-IXPekanbaru - Jakarta, Indonesia | 39 | |
| CNI-IXJakarta, Indonesia | 18 | |
| GPMIXLampung Timur, Indonesia | 13 | |
| IFORTE XchangeJakarta, Indonesia | 7 |
Facilities (2)
The buildings JKT-IX Route Servers lists in PeeringDB, and how many of the exchanges in each it's on.
| NTT Jakarta 2 Data Center (JKT2)Jakarta | 1 of 12 | |
| NTT Jakarta 3 Data Center (JKT3)Jakarta | 1 of 2 |