OTD_OBR_AMANG

BGP inherited
Cluster stats
Netblocks7
All fragments 21 blocks across 4 clusters
Cluster ID210620387
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

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
88.204.216.56/30 OTD_OBR_AMANG RIPE ASSIGNED PA ● low
95.59.163.0/30 OTD_OBR_AMANG RIPE ASSIGNED PA ● low
95.59.163.244/30 OTD_OBR_AMANG RIPE ASSIGNED PA ● low
95.59.165.80/30 OTD_OBR_AMANG RIPE ASSIGNED PA ● low
95.59.233.60/30 OTD_OBR_AMANG RIPE ASSIGNED PA ● low
95.59.234.8/30 OTD_OBR_AMANG RIPE ASSIGNED PA ● low
95.59.234.20/30 OTD_OBR_AMANG RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “OTD OBR” — 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 (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT