Technical-Core-PEP-Devices-P2P-NET
Handle
Cluster stats
| Netblocks | 3 · 765 IPv4 addresses |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 210457916 |
| 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 (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 79.104.248.0/24 | Technical-Core-PEP-Devices-P2P-NET | RIPE | ASSIGNED PA | ● low |
| 79.104.250.0/24 | Technical-Core-PEP-Devices-P2P-NET | RIPE | ASSIGNED PA | ● low |
| 79.104.251.0/24 | Technical-Core-PEP-Devices-P2P-NET | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “Technical Core PEP Devices” — 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.
- Technical-Core-PEP-Devices-Loop-NET 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.
- Technical-Core-PEP-Devices-Loop-NET sub-allocation
NIC Handles
AS3216-MNT
DUMY-RIPE
DUMY-RIPE