APEX Network - JT

Data as of 2026-10-11
BGP inherited
This organisation
Netblocks7
IPv6 3 prefixes (largest 2403:1a00:55:659:a:15:3327:1/128)
Record ID246758654
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
103.28.80.184/32 APEX Network - JT PEERINGDB ASSIGNED ● high
119.11.187.82/32 APEX Network - JT PEERINGDB ASSIGNED ● high
119.11.193.82/32 APEX Network - JT PEERINGDB ASSIGNED ● high
218.100.74.184/32 APEX Network - JT PEERINGDB ASSIGNED ● high
2403:1a00:55:659:a:15:3327:1/128 APEX Network - JT PEERINGDB ASSIGNED ● high
2404:c8:0:a:0:15:3327:1/128 APEX Network - JT PEERINGDB ASSIGNED ● high
2404:c8:0:c:0:15:3327:1/128 APEX Network - JT PEERINGDB ASSIGNED ● high

IPv6 ranges (3)

Footprint over time

3 weekly snapshots · JSON
7 0 netblocks since 2026-09-27
2026-09-27 peak 7 2026-10-11

Network trust

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

NIC Handles

AS153327