Data as of Nov 18, 2026

155.190.34.0/24

4 residential-proxy exits · 30 days

Cisco OpenDNS, LLC · space held by Cisco Systems, Inc.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Corporate gateway
Risk
20 / 100 · Low

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
4
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

10 observations

Proxy providers listing exits

  • GEEKPROXY_FLEX
  • ProxyEmpire
  • Proxyma
  • Shifter

Operators, sellers and brokers

Corporate gateways

NameParentIn 155.190.34.0/24/24s
Cisco UmbrellaCisco
256100%
1

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
155.190.0.0/1665,536OpenDNS-RIPECisco Systems, Inc. (ORG-CSI15-RIPE) · USLEGACYAug 22, 2019rir-abuse@cisco.com
└ 155.190.34.0/24256CIE-NLunknownLEGACYMar 21, 2023rir-abuse@cisco.com
via OpenDNS-RIPE
└ 155.190.34.62/321CIE-LUunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.65/321CIE-BEunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.66/321CIE-BEunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.67/321CIE-BEunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.71/321CIE-PLunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.72/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.73/321CIE-CZunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.74/321CIE-CZunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.77/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.78/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.79/321CIE-GRunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.86/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.87/321CIE-UAunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.88/321CIE-NOunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.96/321CIE-ITunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.97/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.99/321CIE-CHunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.102/321CIE-GRunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.106/321CIE-GRunknownLEGACYFeb 15, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.110/321CIE-DEunknownLEGACYMar 20, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.115/321CIE-DKunknownLEGACYApr 1, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.117/321CIE-GRunknownLEGACYJul 30, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.118/321CIE-GRunknownLEGACYAug 18, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.119/321CIE-BEunknownLEGACYAug 18, 2026rir-abuse@cisco.com
via CIE-NL
└ 155.190.34.120/321CIE-BEunknownLEGACYAug 18, 2026rir-abuse@cisco.com
via CIE-NL

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Oct 2020
Current origin since
Oct 2020 · 6.1 yr
Origin networks
1