Data as of Nov 16, 2026

155.190.35.0/24

No anonymizer space · no proxy exits in 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

Operators, sellers and brokers

Corporate gateways

NameParentIn 155.190.35.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.35.0/24256CIE-DEunknownLEGACYMar 21, 2023rir-abuse@cisco.com
via OpenDNS-RIPE
└ 155.190.35.65/321CIE-LUunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.67/321CIE-GBunknownLEGACYSep 12, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.88/321CIE-NLunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.89/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.92/321CIE-GBunknownLEGACYFeb 27, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.94/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.100/321CIE-BEunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.101/321CIE-BEunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.102/321CIE-BEunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.103/321CIE-BEunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.105/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.120/321CIE-BEunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.121/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.122/321CIE-CZunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.123/321CIE-CZunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.126/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.127/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.133/321CIE-GBunknownLEGACYJul 28, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.138/321CIE-GBunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.141/321CIE-GBunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.146/321CIE-AEunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.147/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.149/321CIE-GBunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.152/321CIE-ITunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.153/321CIE-CHunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.154/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.156/321CIE-GBunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.158/321CIE-GBunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.159/321CIE-ILunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.162/321CIE-GBunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.163/321CIE-GBunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.164/321CIE-GBunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.165/321CIE-GBunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.166/321CIE-GBunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.167/321CIE-GBunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.168/321CIE-GBunknownLEGACYApr 9, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.173/321CIE-GBunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.176/321CIE-BEunknownLEGACYJan 16, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.178/321CIE-GBunknownLEGACYJan 29, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.179/321CIE-GBunknownLEGACYJan 29, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.180/321CIE-GBunknownLEGACYJan 29, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.183/321CIE-GBunknownLEGACYFeb 15, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.184/321CIE-GBunknownLEGACYFeb 15, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.185/321CIE-GBunknownLEGACYFeb 15, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.186/321CIE-GRunknownLEGACYFeb 15, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.187/321CIE-GBunknownLEGACYFeb 20, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.190/321CIE-BEunknownLEGACYMar 20, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.194/321CIE-NLunknownLEGACYApr 1, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.197/321CIE-ILunknownLEGACYApr 8, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.198/321CIE-GBunknownLEGACYApr 22, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.200/321CIE-GRunknownLEGACYJul 30, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.201/321CIE-GRunknownLEGACYAug 18, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.203/321CIE-BEunknownLEGACYAug 18, 2026rir-abuse@cisco.com
via CIE-DE
└ 155.190.35.204/321CIE-BEunknownLEGACYAug 18, 2026rir-abuse@cisco.com
via CIE-DE

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.0 yr
Origin networks
1