TY/CXIX Route Server

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks8
IPv6 5 prefixes (largest 2602:f429:31::1/128)
Cluster ID214594825
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

5 weekly snapshots · JSON
8 +2 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-26

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
23.154.164.129/32 TY/CXIX Route Server PEERINGDB ASSIGNED ● high
33.0.0.1/32 TY/CXIX Route Server PEERINGDB ASSIGNED ● high
33.0.0.65/32 TY/CXIX Route Server PEERINGDB ASSIGNED ● high
2602:f429:31::1/128 TY/CXIX Route Server PEERINGDB ASSIGNED ● high
2602:f92a:1315:1::31/128 TY/CXIX Route Server PEERINGDB ASSIGNED ● high
2602:f92a:1315:1::32/128 TY/CXIX Route Server PEERINGDB ASSIGNED ● high
2a0f:7803:fc60:aaaa::4022:98/128 TY/CXIX Route Server PEERINGDB ASSIGNED ● high
2a0f:7803:fc60:aaaa:0:4022:98:1/128 TY/CXIX Route Server PEERINGDB ASSIGNED ● high

IPv6 ranges (5)

Network trust

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

NIC Handles

AS402298