PL-INOTEL-TB-TG2762-RIPE
Data as of 2026-07-26
Handle
Cluster stats
| Netblocks | 4 |
| IPv6 | 4 prefixes (largest 2a02:78:f0a::/48) |
| All fragments | 26 blocks across 8 clusters |
| Cluster ID | 217076478 |
| 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 · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a02:78:f00:a::/64 | PL-INOTEL-TB-TG2762-RIPE | RIPE | ASSIGNED | ● low |
| 2a02:78:f00:c::/64 | PL-INOTEL-TB-TG2762-RIPE | RIPE | ASSIGNED | ● low |
| 2a02:78:f0a::/48 | PL-INOTEL-TB-TG2762-RIPE | RIPE | ASSIGNED | ● low |
| 2a02:78:f0c::/48 | PL-INOTEL-TB-TG2762-RIPE | RIPE | ASSIGNED | ● low |
IPv6 ranges (4)
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 PL-INOTEL-TB-TG2762-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:f0a::/48 /48 | authorized for AS44514 — INEA sp. z o.o. |
| 2a02:78:f0c::/48 /48 | authorized for AS44514 — INEA sp. z o.o. |
NIC Handles
DUMY-RIPE
DUMY-RIPE
INOTEL-MNT