VIGLEN LTD

VIGLEN-LTD
Data as of 2026-07-26
Registry
Cluster stats
Netblocks7
IPv6 4 prefixes (largest 2a00:2381:f0eb::/48)
All fragments 8 blocks across 2 clusters
Cluster ID214530738
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

6 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-26

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.6.249.32/29 VIGLEN-LTD RIPE ASSIGNED PA ● low
62.6.249.56/29 VIGLEN-LTD RIPE ASSIGNED PA ● low
81.128.182.144/29 VIGLEN RIPE ASSIGNED PA ● low
2a00:2381:f0eb::/56 VIGLEN RIPE ASSIGNED ● low
2a00:2381:f0eb::/48 VIGLEN RIPE AGGREGATED-BY-LIR ● low
2a00:2381:f0eb:100::/56 VIGLEN-LTD RIPE ASSIGNED ● low
2a00:2381:f0eb:200::/56 VIGLEN-LTD RIPE ASSIGNED ● low

IPv6 ranges (4)

Network trust

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

These blocks are registered to VIGLEN LTD 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.

2a00:2381:f0eb::/48 /48 authorized for AS2856 — British Telecommunications Limited
2a00:2381:f0eb::/56 /56 authorized for AS2856 — British Telecommunications Limited
2a00:2381:f0eb:100::/56 /56 authorized for AS2856 — British Telecommunications Limited
2a00:2381:f0eb:200::/56 /56 authorized for AS2856 — British Telecommunications Limited

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE