Servanet AB
HEMAB-NET-2
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 15 blocks across 3 clusters |
| Cluster ID | 205319566 |
| 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 | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 83.166.16.0 – 83.166.21.255 | HEMAB-NET-2 | RIPE | ASSIGNED PA | ● low |
| 83.166.22.0/25 | HEMAB-NET-2 | RIPE | ASSIGNED PA | ● low |
| 83.166.22.128/28 | HEMAB-NET-2 | RIPE | ASSIGNED PA | ● low |
| 83.166.23.0/24 | HEMAB-NET-2 | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (2)
These blocks are registered to HEMAB-NET-2 but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 83.166.16.0 – 83.166.21.255 /21 | authorized for AS31634 — Servanet AB |
| 83.166.23.0/24 /24 | authorized for AS31634 — Servanet AB |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-HEMAB