Servanet AB
HEMAB-NET
BGP inherited
Cluster stats
Netblocks10
All fragments 15 blocks across 3 clusters
Cluster ID192456335
RegistryRIPE
Customersfind 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

Footprint over time

3 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-12

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
83.166.8.0/27 HEMAB-NET RIPE ASSIGNED PA ● low
83.166.8.32/27 HEMAB-NET RIPE ASSIGNED PA ● low
83.166.8.160 – 83.166.8.199 HEMAB-NET RIPE ASSIGNED PA ● low
83.166.8.200/29 HEMAB-NET RIPE ASSIGNED PA ● low
83.166.8.208/29 HEMAB-NET RIPE ASSIGNED PA ● low
83.166.8.216/29 HEMAB-NET RIPE ASSIGNED PA ● low
83.166.8.224/28 HEMAB-NET RIPE ASSIGNED PA ● low
83.166.8.240/29 HEMAB-NET RIPE ASSIGNED PA ● low
83.166.8.248/29 HEMAB-NET RIPE ASSIGNED PA ● low
83.166.9.0 – 83.166.15.255 HEMAB-NET 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 (10 of 10)
Possible discrepancies (1)

These blocks are registered to HEMAB-NET 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.9.0 – 83.166.15.255 /21 authorized for AS31634 — Servanet AB

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-HEMAB