LAYER3 INTEL
Get started
Sign in
Data as of Nov 9, 2026

155.190.51.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
AS36692
Type
Corporate gateway
Risk
20 / 100 · Low

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
1
selling exits here
Oct 10, 2026 – Nov 8, 2026

Exits seen per day

6 observations

Proxy providers listing exits

  • Shifter

Operators, sellers and brokers

Corporate gateways

NameParentIn 155.190.51.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.51.0/24256CIE-SGunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via OpenDNS-RIPE
└ 155.190.51.26/321CIE-KRunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.28/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.29/321CIE-JPunknownLEGACYMar 15, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.30/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.31/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.32/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.33/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.34/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.35/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.36/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.37/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.38/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.39/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.40/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.41/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.42/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.43/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.44/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.45/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.46/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.47/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.48/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.49/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.50/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.51/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.52/321CIE-JPunknownLEGACYFeb 28, 2023rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.76/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.77/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.78/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.81/321CIE-KRunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.98/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.99/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.101/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.102/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.104/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.105/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.106/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.109/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.110/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.111/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.112/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.113/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.114/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.115/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.116/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.117/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.118/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.119/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.120/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.121/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.122/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.125/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.126/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.127/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.128/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.129/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.130/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.131/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.132/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.133/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.134/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.135/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.137/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.139/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.140/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.141/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.142/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.143/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.144/321CIE-VNunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.146/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.147/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.148/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.149/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.150/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.151/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.152/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.156/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.157/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.158/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.162/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.163/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.164/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.165/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.185/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.186/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.187/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.190/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.191/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.192/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.193/321CIE-JPunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.194/321CIE-JPunknownLEGACYJan 28, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.195/321CIE-JPunknownLEGACYJan 29, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.198/321CIE-PHunknownLEGACYFeb 15, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.199/321CIE-JPunknownLEGACYFeb 15, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.200/321CIE-JPunknownLEGACYFeb 15, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.203/321CIE-JPunknownLEGACYMar 3, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.204/321CIE-VNunknownLEGACYMar 20, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.208/321CIE-JPunknownLEGACYMay 27, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.209/321CIE-JPunknownLEGACYMay 27, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.210/321CIE-JPunknownLEGACYJun 27, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.211/321CIE-JPunknownLEGACYJul 14, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.212/321CIE-JPunknownLEGACYJul 14, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.213/321CIE-JPunknownLEGACYJul 14, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.214/321CIE-JPunknownLEGACYJul 30, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.215/321CIE-JPunknownLEGACYJul 30, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.216/321CIE-JPunknownLEGACYJul 30, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.229/321CIE-JPunknownLEGACYAug 18, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.230/321CIE-JPunknownLEGACYAug 18, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.231/321CIE-JPunknownLEGACYAug 18, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.232/321CIE-JPunknownLEGACYSep 22, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.233/321CIE-JPunknownLEGACYSep 22, 2026rir-abuse@cisco.com
via CIE-SG
└ 155.190.51.234/321CIE-JPunknownLEGACYOct 23, 2026rir-abuse@cisco.com
via CIE-SG

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Registry

Holder

Organization
Cisco Systems, Inc.
Handle
ORG-CSI15-RIPE
Range
155.190.0.0/16
Registration type
LEGACY
Record created
Aug 22, 2019
Legacy
yes
Origin network

AS36692

US
Name
Cisco OpenDNS, LLC
Type
Business
Registered
Mar 21, 2006
Domain
opendns.com
Website
www.opendns.com/
Industry
Computer and Information Technology
Spamhaus ASN-DROP
not listed