BREEZE

BGP inherited
Cluster stats
Netblocks7
Registered in United Kingdom (5) · Russia (2)
All fragments 30 blocks across 16 clusters
Cluster ID209438797
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names 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
93.174.132.24/30 BREEZE-NET RIPE ASSIGNED PA ● low
195.11.104.32/30 BREEZE RIPE ASSIGNED PA ● low
195.11.105.40/30 BREEZE RIPE ASSIGNED PA ● low
195.11.111.0/26 BREEZE RIPE ASSIGNED PA ● low
195.11.113.88/30 BREEZE RIPE ASSIGNED PA ● low
195.11.114.44/30 BREEZE RIPE ASSIGNED PA ● low
212.48.148.184/30 BREEZE-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “BREEZE” — 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 16 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: B how networks compare →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-MSTN TI-MNT VODAFONE-WORLDWIDE-MNTNER