asn.dev

Autonomous system

AS14776 YAHOO

Unclassified ARIN

IPv4 addresses 768 2 prefixes
IPv6 prefixes 1 counted as prefixes, not addresses
Countries 1 mostly US
Exchanges 0 recorded by PCH
Upstreams 1 0 downstream
Flagged prefixes 0 none

Summary

Yahoo Holdings

United States · AI-generated

media hosting infrastructure

The same netname as another number in the run, but a different site code in every hostname.

What it's used for

  • One of a run of numbers a large web company uses for its edge sites. 768 IPv4 addresses across two prefixes, one IPv6 prefix, and one observed BGP neighbour.

Notable

  • Both 69.147.86.0/23 and 69.147.66.0/24 carry the netname A-YAHOO-US5, which also appears under a different AS in the same run.
  • All six sampled addresses returned a name, three of them router interfaces.
  • Those are et18-1.bas3-1-edg.daa.yahoo.com, et51.rsw6-1-edg.daa.yahoo.com and et16-1.bas4-1-edg.daa.yahoo.com.
  • One is a serving name, e7.ycpi.daa.yahoo.com.

Interesting

  • Two of those interface names appear under other numbers in this run with only the site code changed, and the third adds a fourth device to the pattern. The template is fixed and the site is the variable, so knowing one site's names is close to knowing every site's.
  • A netname shared across two separate autonomous systems means the registry sees one allocation where routing sees two independent networks. The address paperwork was done once, centrally; the routing was arranged site by site.
  • The serving name is numbered differently at each location too, and it sits in a block announced alongside the routers. The machines answering requests and the equipment carrying them share the same small range.
  • One upstream is the point rather than a weakness: an edge site is meant to be reached from nearby, and a second path would defeat the arrangement.

This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.

Interconnection

Peering at a glance

Full topology · Graph

Internet exchanges

No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.

Transit providers

1 upstream, 0 downstream and 2 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS10310Yahoo Holdings Inc.215

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-15, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 2 prefixes · 768 addresses IPv6 1 prefixes

CountryNamePrefixes
USUnited States of America3

Registry

Allocation record

ARIN · via Atlas (registry + RDAP)
Registry
ARIN
Handle
AS14776
Registry name
YAHOO
Registrant
Yahoo Holdings Inc.
Abuse contact
rir-abuse@yahooinc.com
Registered
2000-02-07
Last changed
2020-07-21
Allocation
assigned

Routing security

RPKI and IRR

Full detail
RPKI
0% valid · 0 valid, 4 with no ROA
ROAs
0 authorising AS14776
ASPA
no ASPA record
IRR
100% registered · 4 of 4 announcements
Route objects
7 naming AS14776

Reputation

Classification and threat

Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.

Spamhaus DROP

Not on ASN-DROP The network as a whole is not listed.

No DROP prefixes None of its announced space is on the DROP prefix list.

Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,781 prefixes, as published 2026-10-16. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.

FBI IC3

No IC3 indicators Nothing from the FBI IC3 feed.

IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.

Elsewhere

Cross-check