A C Gomes-ME
BGP inherited
Cluster stats
Netblocks10
All fragments 115 blocks across 32 clusters
Cluster ID191319823
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
138.99.164.0/24 AS264211 BGP ANNOUNCED ● high
138.99.164.0/22 AS264211 BGP ANNOUNCED ● high
138.99.165.0/24 AS264211 BGP ANNOUNCED ● high
138.99.166.0/24 AS264211 BGP ANNOUNCED ● high
138.99.167.0/24 AS264211 BGP ANNOUNCED ● high
2804:2444::/32 AS264211 BGP ANNOUNCED ● high
138.99.164.32/28 UNKNOWN LACNIC reallocated ● medium
138.99.164.96/30 UNKNOWN LACNIC reallocated ● medium
138.99.165.4/30 UNKNOWN LACNIC reallocated ● medium
2804:2444::/32 UNKNOWN LACNIC allocated ● medium

Network trust

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

These blocks are registered to A C Gomes-ME 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.

2804:2444::/32 /32 authorized for AS264211 — AS264211
2804:2444::/32 /32 authorized for AS264211 — AS264211
138.99.164.0/22 /22 authorized for AS264211 — AS264211
138.99.164.0/24 /24 authorized for AS264211 — AS264211
138.99.165.0/24 /24 authorized for AS264211 — AS264211
138.99.166.0/24 /24 authorized for AS264211 — AS264211
138.99.167.0/24 /24 authorized for AS264211 — AS264211

NIC Handles

AS264211