bgpreport

Network · data from 2026-11-12

AS23816 Yahoo Japan

Registry name: YAHOO - LY Corporation, JP · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS23816, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23816, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
118.151.224.0/19 Valid Other IRR onlyRADB 672 100% 67
202.93.64.0/19 Valid Other IRR onlyRADB 672 100% 67
202.239.0.0/20 Valid Other IRR onlyRADB 672 100% 67
203.141.32.0/20 Valid Other IRR onlyRADB 672 100% 67
203.216.224.0/19 Valid Other IRR onlyRADB 671 100% 67
211.14.12.0/22 Valid Other IRR onlyRADB 670 100% 67
182.22.0.0/17 Valid Other IRR onlyRADB 669 99% 67
2404:a600::/32 Valid Other IRR onlyRADB 634 100% 70

AS-SET

PeeringDB's irr_as_set for AS23816: AS-YAHOO-JP. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS23816 isn't in the set, or no route object for AS23816 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS23816 in itNot covered
AS-YAHOO-JP RADB 5127 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 12 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR118.151.224.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.93.64.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.239.0.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.141.32.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.216.224.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR211.14.12.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR182.22.0.0/17Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2404:a600::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

Route objects with origin AS23816 whose prefix no peer sees AS23816 announce. Many are kept on purpose (backup routes, space announced only in some places).

124.147.32.0/19RADBValid
202.93.64.0/20RADBValid
202.93.80.0/20RADBValid
211.14.20.0/22RADBValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.