Country
—
ASN LANDING PAGE
AS23816
YAHOO - LY Corporation
Last updated · Jul 20, 2026
Total prefixes
8
IPv4 prefixes
7
IPv6 prefixes
1
ASN summary
How to read the scale of AS23816
YAHOO - LY Corporation currently reports 8 prefixes and 27 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
What can an ASN page answer?
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
How should you read the organization and region fields?
YAHOO - LY Corporation is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
How should you verify the AS23816 result?
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
How to verify this ASN result
AS23816 ASN lookupAS23816 BGPAS23816 peersAS23816 prefixesAS23816 upstreamsYAHOO - LY Corporation ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Peers
AS2497
AS2497
—
AS2516
AS2516
—
AS6939
AS6939
—
AS17676
AS17676
—
AS8220
AS8220
—
AS4713
AS4713
—
AS8966
AS8966
—
AS1828
AS1828
—
AS2500
AS2500
—
AS4777
AS4777
—
AS9002
AS9002
—
AS17639
AS17639
—
AS18106
AS18106
—
AS24482
AS24482
—
AS35280
AS35280
—
AS36236
AS36236
—
AS45489
AS45489
—
AS49544
AS49544
—
AS59105
AS59105
—
AS15412
AS15412
—
AS18140
AS18140
—
AS24296
AS24296
—
AS25152
AS25152
—
AS55898
AS55898
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 118.151.224.0/19 | AS23816 | — |
| 182.22.0.0/17 | AS23816 | — |
| 202.239.0.0/20 | AS23816 | — |
| 202.93.64.0/19 | AS23816 | — |
| 203.141.32.0/20 | AS23816 | — |
| 203.216.224.0/19 | AS23816 | — |
| 211.14.12.0/22 | AS23816 | — |
| 2404:a600::/32 | AS23816 | — |
Related ASN pages
AS15169 · Google
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
AS13335 · Cloudflare
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
AS8075 · Microsoft
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
AS16509 · Amazon
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
Related lookups and next steps
Frequently asked questions about this ASN page
What does AS23816 represent?
AS23816 is an autonomous system number. The current source associates it with YAHOO - LY Corporation and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
What are peers, upstreams, and prefixes useful for on the AS23816 page?
They help explain the scale, interconnection depth, and route structure of AS23816. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
What should you do after reviewing AS23816?
Open a concrete IP page to check how the address maps into AS23816, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Related topics
BGP and ASN Basics Guide
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Routing Troubleshooting and Network Analysis
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Cloud Network and ASN Comparison
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.