RNTB

BGP inherited
Cluster stats
Netblocks7
All fragments 11 blocks across 4 clusters
Cluster ID209085596
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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
88.204.170.220/30 RNTB RIPE ASSIGNED PA ● low
89.218.44.248/30 RNTB RIPE ASSIGNED PA ● low
89.218.80.24/30 RNTB RIPE ASSIGNED PA ● low
92.46.46.220/30 RNTB RIPE ASSIGNED PA ● low
95.56.241.220/30 RNTB RIPE ASSIGNED PA ● low
178.88.66.64/30 RNTB RIPE ASSIGNED PA ● low
212.154.195.112/29 RNTB RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “RNTB” — 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.
  • VKFRNTB via JSC Kazakhtelecom sub-allocation
  • Rntb via JSC Kazakhtelecom sub-allocation
  • Kanchipuram via Bharti Airtel Limited sub-allocation
  • Kanchipuram via Bharti Airtel Limited sub-allocation

Network trust

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

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT