TBSH-CLIENT-INFRACAST

Data as of 2026-09-13
BGP inherited
This organisation
Netblocks4 · 272 IPv4 addresses
Also registered under this name 255 netblocks across 137 separate records
Record ID241943290
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
93.91.28.0/24 TBSH-CLIENT-INFRACAST RIPE ASSIGNED PA ● low
213.129.88.112/29 TBSH-CLIENT-INFRACAST RIPE ASSIGNED PA ● low
213.129.88.232/30 TBSH-CLIENT-INFRACAST RIPE ASSIGNED PA ● low
213.129.88.236/30 TBSH-CLIENT-INFRACAST RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (4 of 4)
Possible discrepancies (1)

These blocks are registered to TBSH-CLIENT-INFRACAST but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

93.91.28.0/24 /24 authorized for AS24958 — CYBERFORT LIMITED

NIC Handles

BUNKER-MNT DUMY-RIPE DUMY-RIPE