asn.dev

Autonomous system

AS10230 YAHOO-SG internet content provider

Hosting APNIC

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

Summary

Yahoo (Asia edge)

Singapore · AI-generated

hosting content edge

YAHOO-SG is a small Yahoo network, registered with the flatly descriptive purpose "internet content provider". It is an edge/serving footprint rather than a full site.

What it's used for

  • Fronting Yahoo's consumer properties for users in Asia. RIS sees 3 IPv4 prefixes — 180.222.96.0/24, 180.222.118.0/24 and 180.222.119.0/24, 768 addresses in total — and one IPv6 prefix, 2406:2000:a4::/48, carved from the same 2406:2000::/32 Yahoo uses across the region.

Notable

  • Content hosting, confirmed by both numbers and names. There is exactly 1 observed BGP neighbour: this AS sells transit to nobody and exists only to originate Yahoo's own service addresses. And every sampled PTR is a load balancer or a router interface — slb3-1-prd.in.yahoo.com, vl46.si1.in.yahoo.com, ve-113.si-a5.in.yahoo.com, et2-1.slb11-1-edg.jpa.yahoo.com. slb is a server load balancer, edg an edge node, prd production. Server-farm plumbing, not subscriber access.
  • Three /24s is a deliberately thin footprint. That is the size of an anycast or edge serving cluster, not a data centre: a handful of VIPs behind load balancers, with the actual origin infrastructure elsewhere in Yahoo's estate.

Interesting

  • Read the site codes and the registry handle disagrees with the deployment. The AS is registered as YAHOO-SG (Singapore), but the reverse DNS names India (in.yahoo.com, si1, si-a5) and a Japanese edge (jpa). Nothing is wrong here: a regional registration is an administrative fact, while rDNS records where the boxes actually sit. It is a clean illustration of why a handle should never be read as a location.

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.210

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
SGSingapore3

Registry

Allocation record

APNIC · via Atlas (registry + RDAP)
Registry
APNIC
Handle
AS10230
Registry name
YAHOO-SG
Registrant
Yahoo Inc.
Abuse contact
rir-admin@yahooinc.com
Registered
2008-09-04
Last changed
2021-01-11
Allocation
allocated

Routing security

RPKI and IRR

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

Reputation

Classification and threat

Hosting Datacenter or cloud provider. Addresses are servers, not people.

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