UBER LONDON LIMITED

UBER_LONDON_LIMITED
Data as of 2026-07-26
Registry
Cluster stats
Netblocks8
IPv6 2 prefixes (largest 2001:4d78:104:8::/64)
All fragments 9 blocks across 2 clusters
Cluster ID215567221
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

6 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-26

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
89.187.116.96/28 UBER_LONDON_LIMITED RIPE ASSIGNED PA ● low
89.187.116.192/28 UBER_LONDON_LIMITED RIPE ASSIGNED PA ● low
89.187.118.12/30 UBER_LONDON_LIMITED RIPE ASSIGNED PA ● low
89.187.118.16/30 UBER_LONDON_LIMITED RIPE ASSIGNED PA ● low
193.240.249.96/29 Uber-London-Limited RIPE ASSIGNED PA ● low
194.88.79.96/29 Uber-London-Limited RIPE ASSIGNED PA ● low
2001:4d78:104:8::/64 UBER_LONDON_LIMITED RIPE ASSIGNED ● low
2001:4d78:104:8a::/64 UBER_LONDON_LIMITED RIPE ASSIGNED ● low

IPv6 ranges (2)

Network trust

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

NIC Handles

AB34802-RIPE DUMY-RIPE DUMY-RIPE EQUINIX-FULFIL-MNT EQUINIX-MNT LEVEL3-MNT QUZAUK