PL-INOTEL-TB-NETv6-RIPE
Handle
Cluster stats
| Netblocks | 2 |
| All fragments | 26 blocks across 8 clusters |
| Cluster ID | 206008822 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| 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 |
|---|---|---|---|---|
| 2a02:78:f00:b::/64 | PL-INOTEL-TB-NETv6-RIPE | RIPE | ASSIGNED | ● low |
| 2a02:78:f0b::/48 | PL-INOTEL-TB-NETv6-RIPE | RIPE | ASSIGNED | ● low |
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 PL-INOTEL-TB-NETv6-RIPE 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:78:f0b::/48 /48 | authorized for AS44514 — INEA sp. z o.o. |
NIC Handles
DUMY-RIPE
DUMY-RIPE
INOTEL-MNT