SOUTH-MOUNTAIN-BRANCH-OFFICE

BGP inherited
Cluster stats
Netblocks6
All fragments 8 blocks across 3 clusters
Cluster ID212459945
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 13 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
202.104.125.84/30 SOUTH-MOUNTAIN-BRANCH-OFFICE APNIC ASSIGNED NON-PORTABLE ● high
202.104.125.92/30 SOUTH-MOUNTAIN-BRANCH-OFFICE APNIC ASSIGNED NON-PORTABLE ● high
202.104.125.96/30 SOUTH-MOUNTAIN-BRANCH-OFFICE APNIC ASSIGNED NON-PORTABLE ● high
202.104.125.172/30 SOUTH-MOUNTAIN-BRANCH-OFFICE APNIC ASSIGNED NON-PORTABLE ● high
218.18.102.208/30 SOUTH-MOUNTAIN-BRANCH-OFFICE APNIC ASSIGNED NON-PORTABLE ● high
219.133.197.164/30 SOUTH-MOUNTAIN-BRANCH-OFFICE APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SOUTH MOUNTAIN BRANCH OFFICE” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Network trust

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

NIC Handles

HP324-AP HP324-AP HP327-AP HP327-AP HP329-AP HP329-AP HP330-AP HP330-AP HP331-AP HP331-AP HP332-AP HP332-AP +1 more