VIBO-NET

Handle
Cluster stats
Netblocks10 · 165,887 IPv4 addresses
Registered in Taiwan (8) · Poland (1)
All fragments 11 blocks across 2 clusters
Cluster ID210159570
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
Shared handles clustered on 9 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
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
1.200.0.0/16 VIBO-NET APNIC ALLOCATED PORTABLE ● medium
43.255.180.0/22 VIBO-NET APNIC ALLOCATED PORTABLE ● medium
103.5.32.0/22 VIBO-NET APNIC ALLOCATED PORTABLE ● medium
110.50.128.0/18 VIBO-NET APNIC ALLOCATED PORTABLE ● medium
112.78.64.0/19 VIBO-NET APNIC ALLOCATED PORTABLE ● medium
116.89.128.0/20 VIBO-NET APNIC ALLOCATED PORTABLE ● medium
180.217.0.0/16 VIBO-NET APNIC ALLOCATED PORTABLE ● medium
202.144.208.0/20 VIBO-NET APNIC ALLOCATED PORTABLE ● medium
2403:c300::/32 VIBO-NET APNIC ALLOCATED PORTABLE ● medium
78.10.113.88/29 VIBO RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “VIBO” — 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.

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

AT939-AP BC519-AP DUMY-RIPE DUMY-RIPE MAINT-TW-TWNIC NETIA-MNT PT192-AP VTA1-AP VTA1-AP