VELONET SAS
BGP inherited
Cluster stats
Netblocks10
All fragments 25 blocks across 2 clusters
Cluster ID191619270
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
10 +1 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-12

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.24.186/32 VELONET SAS PEERINGDB ASSIGNED ● high
45.68.30.158/32 VELONET SAS PEERINGDB ASSIGNED ● high
45.175.20.0/24 AS267832 BGP ANNOUNCED ● high
170.245.158.0/24 AS267832 BGP ANNOUNCED ● high
170.245.159.0/24 AS267832 BGP ANNOUNCED ● high
181.189.16.0/23 AS267832 BGP ANNOUNCED ● high
2801:1a:5800:140::8f/128 VELONET SAS PEERINGDB ASSIGNED ● high
2801:1a:5800:142::58/128 VELONET SAS PEERINGDB ASSIGNED ● high
2803:c460::/32 AS267832 BGP ANNOUNCED ● high
2803:c460::/32 UNKNOWN LACNIC allocated ● high

Network trust

what's this?
RPKI hygiene: B how networks compare →
90.0% of checked blocks have valid RPKI ROA coverage (9 of 10)
Possible discrepancies (6)

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

2803:c460::/32 /32 authorized for AS267832 — AS267832
2803:c460::/32 /32 authorized for AS267832 — AS267832
181.189.16.0/23 /23 authorized for AS267832 — AS267832
45.175.20.0/24 /24 authorized for AS267832 — AS267832
170.245.158.0/24 /24 authorized for AS267832 — AS267832
170.245.159.0/24 /24 authorized for AS267832 — AS267832

NIC Handles

AS267832 AS267832