NISAST

BGP inherited
Cluster stats
Netblocks8
Cluster ID210068231
RegistryRIPE
Customersfind 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

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.63.113.96/28 NISAST RIPE ASSIGNED PA ● low
5.63.113.160/28 NISAST RIPE ASSIGNED PA ● low
89.218.69.160/28 NISAST RIPE ASSIGNED PA ● low
89.218.84.192/30 NISAST RIPE ASSIGNED PA ● low
89.218.93.52/30 NISAST RIPE ASSIGNED PA ● low
92.46.70.204/30 NISAST RIPE ASSIGNED PA ● low
95.56.225.0/25 NISAST RIPE ASSIGNED PA ● low
95.59.141.220/30 NISAST RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT