AJBY

BGP inherited
Cluster stats
Netblocks10
Cluster ID209445648
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.5.111.250/32 AJBY RIPE ASSIGNED PA ● low
78.6.143.181/32 AJBY RIPE ASSIGNED PA ● low
78.6.198.88/30 AJBY RIPE ASSIGNED PA ● low
89.118.111.124/30 AJBY RIPE ASSIGNED PA ● low
89.118.111.128/29 AJBY RIPE ASSIGNED PA ● low
89.118.244.48/29 AJBY RIPE ASSIGNED PA ● low
89.119.152.224/28 AJBY RIPE ASSIGNED PA ● low
213.255.5.172/30 AJBY RIPE ASSIGNED PA ● low
213.255.5.184/30 AJBY RIPE ASSIGNED PA ● low
213.255.5.192/29 AJBY 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.
  • AJBY1 via BT Italia S.p.A. sub-allocation
  • AJBY10 via BT Italia S.p.A. sub-allocation
  • AJBY11 via BT Italia S.p.A. sub-allocation
  • TOYOTA-DAJBYCH-CZ via CoProSys a.s. sub-allocation
  • AJBY5 via BT Italia S.p.A. sub-allocation
  • AJBY4 via BT Italia S.p.A. sub-allocation

Network trust

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

NIC Handles

ALBACOM-MNT BTI-MNT DUMY-RIPE DUMY-RIPE