PPPOE-1811-NALICHNAYA-36-LAN

BGP inherited

Cluster stats

Netblocks	2
All fragments	7 blocks across 6 clusters
Cluster ID	208549479
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 (2)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
93.153.182.192/26	PPPOE-1811-NALICHNAYA-36-LAN	RIPE	ASSIGNED PA	● low
93.153.199.128/26	PPPOE-1811-NALICHNAYA-36-LAN	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “PPPOE 1811” — 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.

PPPOE-1811-CITADEL-41-SYS 1 blocks
PPPOE-1811-PISKAREVSKIY38-LAN 1 blocks
PPPOE-1811-KORABLESTROITELEY-19-LAN 1 blocks
PPPOE-1811-CITADEL-43-SYS 1 blocks
PPPOE-1811-PTZ-KOVALEVSKOY-3-SYS 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.

1811 Nikol Pervomaysk 2 Pppoe Sys via PJSC MegaFon sub-allocation
PPPOE-L1HN-1811-SUVOROVSKIY-56-LAN via PJSC MegaFon sub-allocation
Sampsonievskiy 76 Sys via PJSC MegaFon sub-allocation
PPPOE-1811-CITADEL-41-SYS via PJSC MegaFon sub-allocation
PPPOE-1811-PISKAREVSKIY38-LAN via PJSC MegaFon sub-allocation
PPPOE-1811-KORABLESTROITELEY-19-LAN via PJSC MegaFon sub-allocation
PPPOE-1811-CITADEL-43-SYS via PJSC MegaFon sub-allocation
PPPOE-HN-1811-NIKOL-OKTYABORG-17-LAN via PJSC MegaFon sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (2 of 2)

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE PSTAR-MNT