bgpreport

Network · data from 2026-11-12

AS45501 YAHOO-CORP-SG-AS-AP - Yahoo Corp Network

Registry name: YAHOO-CORP-SG-AS-AP - Yahoo Corp Network, SG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45501, 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.
2406:2000:ef64::/48 No ROA Other IRR onlyRADB 633 100% 69
2406:2000:efa5::/48 No ROA Other IRR onlyRADB 633 100% 69
117.104.189.0/24 No ROA RIR databaseAPNIC 671 100% 67
202.89.121.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67

AS-SET

AS45501 isn't in PeeringDB, where networks name their AS-SET.

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 14 are in fix.csv.

  • ROA: none4
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none2406:2000:ef64::/48No ROA covers it. Add a ROA for AS45501, maxLength 48.633 of 636
Route object: RIR2406:2000:ef64::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2406:2000:efa5::/48No ROA covers it. Add a ROA for AS45501, maxLength 48.633 of 636
Route object: RIR2406:2000:efa5::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none117.104.189.0/24No ROA covers it. Add a ROA for AS45501, maxLength 24.671 of 673
ROA: none202.89.121.0/24No ROA covers it. Add a ROA for AS45501, maxLength 24.671 of 673

Route objects not announced

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

117.104.188.0/24RADBNo ROA
202.89.120.0/22APNICNo ROA
202.89.120.0/23RADBNo ROA
202.89.120.0/24RADBNo ROA
203.110.237.0/24RADBNo ROA
2406:2000:ef96::/48RADBNo ROA
2406:2000:efb3::/48RADBNo ROA
2406:2000:efba::/48RADBNo ROA

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.