R DE MELO NEVES CONEX - ME

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks5 · 1,026 IPv4 addresses
IPv6 2 prefixes (largest 2001:12f8:0:2::208/128)
Also registered under this name 21 netblocks across 3 separate records
Record ID239827290
RegistryPEERINGDB
Customerssee who runs inside 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 · report an issue

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.80.208/32 R DE MELO NEVES CONEX - ME PEERINGDB ASSIGNED ● high
187.16.216.86/32 R DE MELO NEVES CONEX - ME PEERINGDB ASSIGNED ● high
2001:12f8::86/128 R DE MELO NEVES CONEX - ME PEERINGDB ASSIGNED ● high
2001:12f8:0:2::208/128 R DE MELO NEVES CONEX - ME PEERINGDB ASSIGNED ● high
138.97.192.0/22 R DE MELO NEVES CONEX - ME ARIN ALLOCATED ● low

IPv6 ranges (2)

CIDR
2001:12f8:0:2::208/128
2001:12f8::86/128

Footprint over time

3 weekly snapshots · JSON
11 +5 netblocks since 2026-07-05
2026-07-05 peak 11 2026-07-12

Network trust

what's this?
RPKI hygiene: B how networks compare →
80.0% of checked blocks have valid RPKI ROA coverage (4 of 5)
No discrepancies found among checked blocks.

NIC Handles

20799239000180 AS264200 YRRNO2 YRRNO2 YRRNO2