CONEX TV

Data as of 2026-08-30
BGP inherited
Cluster stats
Netblocks8
IPv6 4 prefixes (largest 2803:350:ccc:c::23/128)
All fragments 10 blocks across 2 clusters
Cluster ID233795838
RegistryPEERINGDB
Customersfind customers using 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

Footprint over time

10 weekly snapshots · JSON
8 -3 netblocks since 2026-07-05
2026-07-05 peak 11 2026-08-30

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
38.3.128.23/32 CONEX TV PEERINGDB ASSIGNED ● high
38.190.102.1/32 CONEX TV PEERINGDB ASSIGNED ● high
38.190.102.2/32 CONEX TV PEERINGDB ASSIGNED ● high
38.190.102.10/32 CONEX TV PEERINGDB ASSIGNED ● high
2803:350:ccc:c::23/128 CONEX TV PEERINGDB ASSIGNED ● high
2803:9450:40f:f::1/128 CONEX TV PEERINGDB ASSIGNED ● high
2803:9450:40f:f::2/128 CONEX TV PEERINGDB ASSIGNED ● high
2803:9450:40f:f::10/128 CONEX TV PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

Network trust

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

NIC Handles

AS273133