NET UBER TELECOM

Data as of 2026-09-13
BGP inherited
This organisation
Netblocks7 · 256 IPv4 addresses
IPv6 3 prefixes (largest 2804:8c58::/32)
Record ID240861813
RegistryBGP
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
186.209.96.0/24 NET UBER TELECOM BGP ANNOUNCED ● high
2804:8c58::/33 NET UBER TELECOM BGP ANNOUNCED ● high
2804:8c58::/32 NET UBER TELECOM BGP ANNOUNCED ● high
2804:8c58:8000::/33 NET UBER TELECOM BGP ANNOUNCED ● high
186.209.96.128/26 UNKNOWN LACNIC reallocated ● medium
186.209.96.204/30 UNKNOWN LACNIC reallocated ● medium
186.209.96.224/30 UNKNOWN LACNIC reallocated ● medium

IPv6 ranges (3)

Footprint over time

2 weekly snapshots · JSON
10 +2 netblocks since 2026-07-12
2026-07-12 peak 10 2026-09-13

Network trust

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

NIC Handles

12227767000137 AS273797 RMFJU17 RMFJU17 RMFJU17