NURBANK

BGP inherited

Cluster stats

Netblocks	9 · 343 IPv4 addresses
All fragments	12 blocks across 2 clusters
Cluster ID	208862173
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

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

Footprint over time

5 weekly snapshots · JSON

8 0 netblocks since 2026-07-05

2026-07-05 peak 8 2026-07-19

IP Ranges (9)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
88.204.130.64/29	NURBANK	RIPE	ASSIGNED PA	● low
88.204.224.156/30	NURBANK	RIPE	ASSIGNED PA	● low
89.218.46.96/27	NURBANK	RIPE	ASSIGNED PA	● low
92.46.63.48/30	NURBANK	RIPE	ASSIGNED PA	● low
92.46.214.128/30	NURBANK	RIPE	ASSIGNED PA	● low
95.56.231.208/30	NURBANK	RIPE	ASSIGNED PA	● low
193.193.234.0/24	NURBANK-NET	RIPE	ASSIGNED PA	● low
212.154.141.64/27	NURBANK	RIPE	ASSIGNED PA	● low
212.154.156.192/29	NURBANK	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

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

Nurbank JSC 3 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.

Nurbank via JSC Kazakhtelecom sub-allocation
AONURBANK via JSC Kazakhtelecom sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

ASTEL-MNT DUMY-RIPE DUMY-RIPE KNIC-MNT