PARTIZAN-NET

BGP inherited

Cluster stats

Netblocks	6
All fragments	18 blocks across 2 clusters
Cluster ID	209030982
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 5 shared RIR contact/maintainer handles
Registry names	2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON

6 0 netblocks since 2026-07-05

2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
93.87.35.160/30	PARTIZAN_NET	RIPE	ASSIGNED PA	● low
195.178.63.0/29	PARTIZAN-NET	RIPE	ASSIGNED PA	● low
212.200.74.40/29	PARTIZAN-NET	RIPE	ASSIGNED PA	● low
212.200.214.132/30	PARTIZAN_NET	RIPE	ASSIGNED PA	● low
213.240.48.32/28	PARTIZAN-NET	RIPE	ASSIGNED PA	● low
213.240.49.240/28	PARTIZAN-NET	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

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

PARTIZAN-TECHNOLOGY-INC 12 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.

HOTEL-PARTIZAN-NET via Slovak Telekom, a.s. sub-allocation
Partizan via TELEKOM SRBIJA a.d. sub-allocation
PRVI-PARTIZAN-NET via TELEKOM SRBIJA a.d. sub-allocation
x_KOSARKASKI_KLUB_PARTIZAN_x via TELEKOM SRBIJA a.d. sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

AS8400-MNT DUMY-RIPE DUMY-RIPE EUNETYU-MNT TELEKOM-MNT