RPVS

BGP inherited
Cluster stats
Netblocks8
Cluster ID209855951
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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.4.196.196/30 RPVS RIPE ASSIGNED PA ● low
78.4.199.104/29 RPVS RIPE ASSIGNED PA ● low
78.6.253.132/30 RPVS RIPE ASSIGNED PA ● low
78.7.244.200/30 RPVS RIPE ASSIGNED PA ● low
89.119.240.24/29 RPVS RIPE ASSIGNED PA ● low
213.213.47.240/29 RPVS RIPE ASSIGNED PA ● low
217.220.77.48/29 RPVS RIPE ASSIGNED PA ● low
217.220.77.152/30 RPVS 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.
  • RPVSERVICOS via NOS COMUNICACOES, S.A. sub-allocation

Network trust

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

NIC Handles

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