Verge
Cluster stats
Netblocks13
All fragments 69 blocks across 4 clusters
Cluster ID193389705
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (13)

⬇ export CSV
CIDR Org name Registry Status Confidence
43.243.21.129/32 Verge PEERINGDB ASSIGNED ● high
103.26.68.186/32 Verge PEERINGDB ASSIGNED ● high
103.180.190.9/32 Verge PEERINGDB ASSIGNED ● high
202.77.88.121/32 Verge PEERINGDB ASSIGNED ● high
2001:7fa:11:6:2:4f28:0:1/128 Verge PEERINGDB ASSIGNED ● high
2001:dea:0:10::ba/128 Verge PEERINGDB ASSIGNED ● high
2001:df0:680:5::78/128 Verge PEERINGDB ASSIGNED ● high
2001:df0:680:11::9/128 Verge PEERINGDB ASSIGNED ● high
103.204.2.0/27 Verge APNIC ASSIGNED NON-PORTABLE ● low
103.204.2.224/27 Verge APNIC ALLOCATED NON-PORTABLE ● low
103.204.3.0/24 Verge APNIC ASSIGNED NON-PORTABLE ● low
2400:ff60::/33 Verge APNIC ALLOCATED NON-PORTABLE ● low
2400:ff60:8000::/33 Verge APNIC ALLOCATED NON-PORTABLE ● low

Network trust

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

NIC Handles

AS151336 AV575-AP MAINT-VERGE-NZ VIL1-AP VIL1-AP VIL1-AP