byBrick-Hosting

Handle
Cluster stats
Netblocks8
All fragments 12 blocks across 3 clusters
Cluster ID210497864
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
79.99.224.101 – 79.99.224.105 byBrick-Hosting RIPE ASSIGNED PA ● low
79.99.224.106/32 byBrick-Hosting RIPE ASSIGNED PA ● low
79.99.224.107/32 byBrick-Hosting RIPE ASSIGNED PA ● low
79.99.224.108/32 byBrick-Hosting RIPE ASSIGNED PA ● low
79.99.224.109/32 byBrick-Hosting RIPE ASSIGNED PA ● low
79.99.224.110/32 byBrick-Hosting RIPE ASSIGNED PA ● low
79.99.224.111 – 79.99.224.112 byBrick-Hosting RIPE ASSIGNED PA ● low
79.99.224.113/32 byBrick-Hosting RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “byBrick” — 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.
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.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-BYBRICK