AD-HOC-HOLDING
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 29 blocks across 14 clusters |
| Cluster ID | 205671881 |
| 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 (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 109.73.24.72/29 | AD-HOC-HOLDING | RIPE | ASSIGNED PA | ● low |
| 2a02:2250:1f0:f100::/56 | AD-HOC-HOLDING | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “AD HOC” — 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.
- AD_HOC_BEHEER_BV 6 blocks
- Ad Hoc Software Pty. Ltd. 3 blocks
- AD-HOC-BEST-SERVICES-POESSNECK-NET 3 blocks
- AD-HOC-NETWORK 2 blocks
- AD-HOC-BEST-SERVICE-NET 2 blocks
- AD-HOC-BAUWERK--NET 2 blocks
- AD-HOC-APPLIED-INFORMATICS 2 blocks
- AD-HOC-RESEARCH 2 blocks
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to AD-HOC-HOLDING 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:2250:1f0:f100::/56 /56 | authorized for AS196714 — Thueringer Netkom GmbH |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-TNETKOM