PJSC Rostelecom

Static_PPPoE_pool_4

BGP inherited

Cluster stats

Netblocks	1
All fragments	7 blocks across 7 clusters
Cluster ID	204893023
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 (1)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
85.192.184.0/24	Static_PPPoE_pool_4	RIPE	ASSIGNED PA	● medium

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “Static PPPoE pool” — 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.

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.

Static_PPPoE_pool via PJSC Rostelecom sub-allocation
Static_PPPoE_pool_3 via PJSC Rostelecom sub-allocation
Static_PPPoE_pool_5 via PJSC Rostelecom sub-allocation
Static_PPPoE_pool_7 via PJSC Rostelecom sub-allocation
Static_PPPoE_pool_2 via PJSC Rostelecom sub-allocation
Static_PPPoE_pool_8 via PJSC Rostelecom sub-allocation
Magnet Static Pool Rte1 Pppoe via Magnet Networks Limited 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)

RPKI-inferred operator PJSC Rostelecom

Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE ESOO-MNT