Data as of Nov 17, 2026

151.186.145.0/24

No anonymizer space · no proxy exits in 30 days

Amazon.com, Inc. · 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 151.186.145.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
151.186.0.0/1665,536OpenDNS-RIPECisco Systems, Inc. (ORG-CSI15-RIPE) · USLEGACYSep 2, 2021rir-abuse@cisco.com
└ 151.186.144.0/204,096CISCO-CIE-NATAAS-12unknownLEGACYJun 12, 2024rir-abuse@cisco.com
via OpenDNS-RIPE
└ 151.186.145.0/24256CISCO-CIE-NATAAS-12unknownLEGACYJun 12, 2024rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.22/321CIE-GBunknownLEGACYApr 7, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.27/321CIE-GBunknownLEGACYMay 27, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.28/321CIE-ESunknownLEGACYJun 10, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.29/321CIE-ESunknownLEGACYJun 10, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.30/321CIE-DEunknownLEGACYJun 10, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.33/321CIE-BEunknownLEGACYJul 14, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.39/321CIE-ATunknownLEGACYSep 22, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.40/321CIE-NLunknownLEGACYSep 24, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.41/321CIE-MAunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.42/321CIE-MAunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.43/321CIE-PTunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.44/321CIE-PTunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.53/321CIE-DEunknownLEGACYOct 23, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.54/321CIE-GBunknownLEGACYOct 23, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.55/321CIE-GBunknownLEGACYOct 23, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.57/321CIE-ADunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.58/321CIE-ADunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.61/321CIE-NGunknownLEGACYNov 13, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.86/321CIE-NLunknownLEGACYApr 7, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.87/321CIE-BEunknownLEGACYApr 7, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.92/321CIE-ESunknownLEGACYJun 10, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.96/321CIE-DEunknownLEGACYJul 14, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.97/321CIE-DEunknownLEGACYJul 14, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.99/321CIE-BEunknownLEGACYJul 30, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.100/321CIE-GBunknownLEGACYAug 18, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.104/321CIE-MAunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.105/321CIE-MAunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.106/321CIE-PTunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.107/321CIE-PTunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.119/321CIE-GBunknownLEGACYOct 23, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.120/321CIE-IQunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.121/321CIE-IQunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.145.122/321CIE-GBunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12

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
Jul 2024
Current origin since
Jul 2024 · 2.3 yr
Origin networks
1