IDNIC AS4622

Data as of 2026-08-16
BGP inherited
Cluster stats
Netblocks12
IPv6 6 prefixes (largest 2001:7fa:2:5::1e1/128)
Cluster ID222476964
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

8 weekly snapshots · JSON
12 0 netblocks since 2026-07-05
2026-07-05 peak 12 2026-08-16

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
123.108.8.3/32 IDNIC AS4622 PEERINGDB ASSIGNED ● high
123.108.8.159/32 IDNIC AS4622 PEERINGDB ASSIGNED ● high
123.108.9.4/32 IDNIC AS4622 PEERINGDB ASSIGNED ● high
123.108.9.225/32 IDNIC AS4622 PEERINGDB ASSIGNED ● high
123.108.11.88/32 IDNIC AS4622 PEERINGDB ASSIGNED ● high
123.108.11.89/32 IDNIC AS4622 PEERINGDB ASSIGNED ● high
2001:7fa:2:5::3/128 IDNIC AS4622 PEERINGDB ASSIGNED ● high
2001:7fa:2:5::f/128 IDNIC AS4622 PEERINGDB ASSIGNED ● high
2001:7fa:2:5::9f/128 IDNIC AS4622 PEERINGDB ASSIGNED ● high
2001:7fa:2:5::1e1/128 IDNIC AS4622 PEERINGDB ASSIGNED ● high
2001:7fa:2:5::374/128 IDNIC AS4622 PEERINGDB ASSIGNED ● high
2001:7fa:2:5::375/128 IDNIC AS4622 PEERINGDB ASSIGNED ● high

IPv6 ranges (6)

Network trust

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

NIC Handles

AS4622