URBANACCESS

Handle
Cluster stats
Netblocks10
All fragments 12 blocks across 2 clusters
Cluster ID207727717
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
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

Footprint over time

4 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-13

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
36.91.197.20/32 URBANACCESS PEERINGDB ASSIGNED ● high
103.30.172.230/32 URBANACCESS PEERINGDB ASSIGNED ● high
103.133.149.130/32 URBANACCESS PEERINGDB ASSIGNED ● high
119.11.184.173/32 URBANACCESS PEERINGDB ASSIGNED ● high
123.108.9.34/32 URBANACCESS PEERINGDB ASSIGNED ● high
218.100.31.215/32 URBANACCESS PEERINGDB ASSIGNED ● high
2001:7fa:2:5::122/128 URBANACCESS PEERINGDB ASSIGNED ● high
2001:df0:f080:cdc:cdc:cdc:cdc:32/128 URBANACCESS PEERINGDB ASSIGNED ● high
2001:df7:3400::429/128 URBANACCESS PEERINGDB ASSIGNED ● high
2404:c8:0:a:0:14:429:1/128 URBANACCESS PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS140429