KRS-REGION-ELECTROSILA-7

BGP inherited

Cluster stats

Netblocks	2 · 510 IPv4 addresses
All fragments	8 blocks across 7 clusters
Cluster ID	209847821
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
95.137.30.0/24	KRS-REGION-ELECTROSILA-7	RIPE	ASSIGNED PA	● low
95.137.31.0/24	KRS-REGION-ELECTROSILA-7	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “KRS REGION ELECTROSILA” — 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.

KRS-REGION-ELECTROSILA-1 via PJSC MegaFon sub-allocation
KRS-REGION-ELECTROSILA-2 via PJSC MegaFon sub-allocation
KRS-REGION-ELECTROSILA-3 via PJSC MegaFon sub-allocation
KRS-REGION-ELECTROSILA-4 via PJSC MegaFon sub-allocation
KRS-REGION-ELECTROSILA-5 via PJSC MegaFon sub-allocation
KRS-REGION-ELECTROSILA-6 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)

RPKI-inferred operator PJSC MegaFon

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 MNT-MF-NWGSM