Pool8
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 4 blocks across 3 clusters |
| Cluster ID | 205392541 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.41.34.232/29 | Pool8 | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “Pool8” — 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.
- POOL8-BAS6-CONTEXORANGE 2 blocks
- Pool8-BAS5-CONTEXT-ORANGE 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- CPE Pool8 via SWU TeleNet GmbH sub-allocation
- Clientpool8 via Lighthouse Networks Limited sub-allocation
- TRANSIP-NL-VPS-POOL8-MANAGEMENT via Signet B.V. sub-allocation
- URAL_TTK-RTL-POOL8 via Limited Liability Company "TTK-Svyaz" sub-allocation
- Ipv4 sub-allocation
- FESR-POOL8-NET via The Constant Company, LLC sub-allocation
- Static via TeleData GmbH sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
No discrepancies found among checked blocks.
NIC Handles
AF64616-MNT
DUMY-RIPE
DUMY-RIPE
it-nexusway-1-mnt