BURO

BGP inherited
Cluster stats
Netblocks6
Registered in KZ (3) · Russia (3)
All fragments 56 blocks across 31 clusters
Cluster ID209122874
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.200.142.0/30 BURO RIPE ASSIGNED PA ● low
85.90.124.72/29 Buro-NET RIPE ASSIGNED PA ● low
85.119.78.176/28 BURO-NET RIPE ASSIGNED PA ● low
88.204.136.144/29 BURO RIPE ASSIGNED PA ● low
178.88.69.160/27 BURO RIPE ASSIGNED PA ● low
194.84.176.96/28 AS-BURO-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “BURO” — 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.
Combined view of all 31 name-family clusters →
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

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

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT MNT-TELECOM-TZ NTSI-MNT ROSPRINT-NCC