UNDP-FILIAL-AF-UN-NEW-YORK-NET
BGP inherited
Cluster stats
Netblocks6
All fragments 193 blocks across 101 clusters
Cluster ID193788568
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-06

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
2.106.80.160/28 UNDP-FILIAL-AF-UN-NEW-YORK-NET RIPE ASSIGNED PA ● low
80.62.119.0/24 UNDP-FILIAL-AF-UN-NEW-YORK-NET RIPE ASSIGNED PA ● low
93.165.155.176/28 UNDP-FILIAL-AF-UN-NEW-YORK-NET RIPE ASSIGNED PA ● low
93.178.184.96/28 UNDP-FILIAL-AF-UN-NEW-YORK-NET RIPE ASSIGNED PA ● low
128.76.62.80/28 UNDP-FILIAL-AF-UN-NEW-YORK-NET RIPE ASSIGNED PA ● low
195.215.85.192/27 UNDP-FILIAL-AF-UN-NEW-YORK-NET RIPE ASSIGNED PA ● low

Network trust

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

These blocks are registered to UNDP-FILIAL-AF-UN-NEW-YORK-NET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

80.62.119.0/24 /24 authorized for AS3292 — TDC Holding A/S

NIC Handles

DUMY-RIPE DUMY-RIPE TDK-MNT