Arax-Impex s.r.l.

PPPoE-217-26-166

BGP inherited

Cluster stats

Netblocks	1
All fragments	4 blocks across 4 clusters
Cluster ID	208177627
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
217.26.166.0/24	PPPoE-217-26-166	RIPE	ASSIGNED PA	● medium

Possibly related to this organisation

what's this?

Same name family

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

VYBORG-PPPOE-SYS via PJSC MegaFon sub-allocation
1811 Nikol Pervomaysk 2 Pppoe Sys via PJSC MegaFon sub-allocation
D2801-KNG-GAKUNA-2-PPPOE-SYS via PJSC MegaFon sub-allocation
D7206-PSK-OSTROV3-PPPOE-SYS via PJSC MegaFon sub-allocation
1841 Kovalevskaya Pppoe Sys via PJSC MegaFon sub-allocation
PPPOE-NIKOL-OKTYABORG-9-SYS via PJSC MegaFon sub-allocation
PPPOE-CITADELSKOE-43-SYS via PJSC MegaFon sub-allocation
POL-PPPOE-USSK-UNLIM-3-NET via PJSC Rostelecom 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 Arax-Impex s.r.l.

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

ARAXCOM-MNT DUMY-RIPE DUMY-RIPE