Data as of Nov 21, 2026

151.186.50.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
Recent change
New origin Sep 2026
its first announcement on record

Operators, sellers and brokers

Corporate gateways

NameParentIn 151.186.50.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.48.0/204,096CISCO-CIE-NATAAS-13unknownLEGACYSep 16, 2026rir-abuse@cisco.com
via OpenDNS-RIPE
└ 151.186.50.0/24256CISCO-CIE-NATAAS-13unknownLEGACYSep 16, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.1/321CIE-JPunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.2/321CIE-JPunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.3/321CIE-JPunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.4/321CIE-JPunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.5/321CIE-AUunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.6/321CIE-JPunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.7/321CIE-PHunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.8/321CIE-PHunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.9/321CIE-PHunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.13/321CIE-AUunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.14/321CIE-AUunknownLEGACYNov 13, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.15/321CIE-AUunknownLEGACYNov 12, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.131/321CIE-JPunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.132/321CIE-AUunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.133/321CIE-AUunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.134/321CIE-PHunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.135/321CIE-PHunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.136/321CIE-PHunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.139/321CIE-AUunknownLEGACYNov 9, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.141/321CIE-AUunknownLEGACYNov 12, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13
└ 151.186.50.143/321CIE-AUunknownLEGACYNov 12, 2026rir-abuse@cisco.com
via CISCO-CIE-NATAAS-13

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
Sep 2026
Current origin since
Sep 2026 · 2 mo
Origin networks
1