velia

BGP inherited
Cluster stats
Netblocks7
All fragments 1,054 blocks across 8 clusters
Cluster ID210763503
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 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
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
85.195.92.154/31 velia RIPE ASSIGNED PA ● high
85.195.123.24/29 velia RIPE ASSIGNED PA ● high
85.195.126.0/30 velia RIPE ASSIGNED PA ● high
85.195.126.4/30 velia RIPE ASSIGNED PA ● high
2a01:7a0:2:1681::/64 velia RIPE ASSIGNED ● high
195.82.32.144/29 Velia RIPE ASSIGNED PA ● low
2a02:ae0:0:d00::/56 Velia RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “velia” — 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 (7 of 7)
Possible discrepancies (1)

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

2a02:ae0:0:d00::/56 /56 authorized for AS8375 — Telehouse Deutschland GmbH

NIC Handles

DUMY-RIPE DUMY-RIPE FGK-MNT ORG-VA29360-RIPE lir-de-telehouse-1-MNT