JKT-IX Route Servers

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks7
IPv6 3 prefixes (largest 2404:c8:0:a:0:13:7295:1/128)
Record ID239847767
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
119.11.184.101/32 JKT-IX Route Servers PEERINGDB ASSIGNED ● high
119.11.184.102/32 JKT-IX Route Servers PEERINGDB ASSIGNED ● high
119.11.185.222/32 JKT-IX Route Servers PEERINGDB ASSIGNED ● high
119.11.193.101/32 JKT-IX Route Servers PEERINGDB ASSIGNED ● high
2404:c8:0:a:0:13:7295:1/128 JKT-IX Route Servers PEERINGDB ASSIGNED ● high
2404:c8:0:a:0:13:7295:2/128 JKT-IX Route Servers PEERINGDB ASSIGNED ● high
2404:c8:0:c:0:13:7295:1/128 JKT-IX Route Servers PEERINGDB ASSIGNED ● high

IPv6 ranges (3)

Footprint over time

11 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-09-06

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

AS137295