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

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

Operators, sellers and brokers

Corporate gateways

NameParentIn 151.186.151.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.151.0/24256CISCO-CIE-NATAAS-12unknownLEGACYJun 12, 2024rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.23/321CIE-DEunknownLEGACYFeb 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.24/321CIE-HUunknownLEGACYFeb 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.25/321CIE-LYunknownLEGACYFeb 15, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.29/321CIE-RSunknownLEGACYApr 22, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.30/321CIE-RSunknownLEGACYApr 22, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.31/321CIE-FRunknownLEGACYApr 22, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.32/321CIE-RSunknownLEGACYApr 22, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.34/321CIE-AEunknownLEGACYJun 27, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.35/321CIE-HUunknownLEGACYJun 27, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.38/321CIE-ATunknownLEGACYJul 30, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.40/321CIE-KEunknownLEGACYAug 19, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.41/321CIE-CZunknownLEGACYSep 16, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.42/321CIE-CZunknownLEGACYSep 16, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.43/321CIE-ROunknownLEGACYSep 16, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.44/321CIE-ROunknownLEGACYSep 16, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.46/321CIE-ATunknownLEGACYSep 22, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.47/321CIE-GRunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.48/321CIE-GRunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.49/321CIE-TRunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.50/321CIE-TRunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.51/321CIE-UAunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.52/321CIE-UAunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.60/321CIE-CZunknownLEGACYOct 23, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.61/321CIE-CYunknownLEGACYOct 23, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.63/321CIE-JOunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.86/321CIE-DEunknownLEGACYFeb 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.90/321CIE-CHunknownLEGACYMar 20, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.91/321CIE-RSunknownLEGACYApr 22, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.92/321CIE-FRunknownLEGACYApr 22, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.93/321CIE-RSunknownLEGACYApr 22, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.94/321CIE-RSunknownLEGACYApr 22, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.95/321CIE-FRunknownLEGACYApr 22, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.97/321CIE-DEunknownLEGACYJun 27, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.103/321CIE-ILunknownLEGACYAug 19, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.104/321CIE-CZunknownLEGACYSep 16, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.105/321CIE-CZunknownLEGACYSep 16, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.106/321CIE-ROunknownLEGACYSep 16, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.107/321CIE-ROunknownLEGACYSep 16, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.110/321CIE-GRunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.111/321CIE-GRunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.112/321CIE-TRunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.113/321CIE-TRunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.114/321CIE-UAunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.115/321CIE-UAunknownLEGACYOct 3, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.125/321CIE-IQunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.126/321CIE-KWunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.127/321CIE-IQunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.129/321CIE-OMunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.130/321CIE-JOunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.131/321CIE-OMunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.193/321CIE-KWunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-12
└ 151.186.151.195/321CIE-FRunknownLEGACYNov 13, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Aug 2025
Current origin since
Aug 2025 · 1.2 yr
Origin networks
1