BAHAG
Data as of 2026-11-08
BGP inherited
This organisation
| Netblocks | 6 |
| IPv6 | 2 prefixes (largest 2a02:2e0:3ee::/48) |
| Also registered under this name | 15 netblocks across 8 separate records |
| Record ID | 265894978 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 82.98.71.92/30 | bahag-net | RIPE | ASSIGNED PA | ● low |
| 82.98.71.132/30 | bahag-net | RIPE | ASSIGNED PA | ● low |
| 213.83.18.128/28 | BAHAG | RIPE | ASSIGNED PA | ● low |
| 213.83.18.144/28 | BAHAG | RIPE | ASSIGNED PA | ● low |
| 2a02:2e0:3ee::/48 | BAHAG-NET | RIPE | ASSIGNED | ● low |
| 2a02:2e0:3ef::/48 | BAHAG | RIPE | ASSIGNED | ● low |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(6 of 6)
Possible discrepancies (2)
These blocks are registered to BAHAG 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.
| 2a02:2e0:3ef::/48 /48 | authorized for AS12306 — Plus.line AG |
| 2a02:2e0:3ee::/48 /48 | authorized for AS206564 — Plus.line AG |
NIC Handles
DUMY-RIPE
DUMY-RIPE
PLUSLINE-MNT