users_with_static_IP-addresses
BGP inherited
Cluster stats
| Netblocks | 6 · 3,322 IPv4 addresses |
| All fragments | 8 blocks across 3 clusters |
| Cluster ID | 211478243 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 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
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 |
|---|---|---|---|---|
| 92.36.200.0/21 | users_with_static_IP-addresses | RIPE | LIR-PARTITIONED PA | ● low |
| 92.36.201.0/24 | users_with_static_IP_addresses | RIPE | ASSIGNED PA | ● low |
| 92.36.204.0/24 | users_with_static_IP-addresses | RIPE | ASSIGNED PA | ● low |
| 92.36.205.0/24 | users_with_static_IP-addresses | RIPE | ASSIGNED PA | ● low |
| 92.36.206.0/24 | users_with_static_IP-addresses | RIPE | ASSIGNED PA | ● low |
| 92.36.207.0/24 | users_with_static_IP-addresses | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “users with static IP” — 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.
- users_with_static_IP_addressess 1 blocks
- users_with_static_IP-adresses 1 blocks
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.
- users_with_static_IP_addressess via BH Telecom d.d. Sarajevo sub-allocation
- users_with_static_IP-adresses via BH Telecom d.d. Sarajevo sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(6 of 6)
RPKI-inferred operator
BH Telecom d.d. Sarajevo
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
BIHNET-DNS
DUMY-RIPE
DUMY-RIPE