bgpreport

Network · data from 2026-11-12

AS140469 Wahyu Adidaya Network

Registry name: WANET-AS-ID - PT Wahyu Adidaya Network, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140469, 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:4940::/32 Valid None 636 100% 70
103.153.190.0/24 Valid Other IRR onlyRADB 673 100% 69
103.153.191.0/24 Valid Other IRR onlyRADB 673 100% 69
103.153.190.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
151.242.156.0/24 Valid RIR databaseRADB, RIPE 673 100% 70
201.3.124.0/24 Valid RIR databaseALTDB, RIPE 673 100% 69
201.3.125.0/24 Valid RIR databaseRIPE 673 100% 69
201.3.126.0/24 Valid RIR databaseRIPE 673 100% 67
143.109.52.0/24 Valid RIR databaseARIN, RADB 672 100% 68

AS-SET

PeeringDB's irr_as_set for AS140469: AS-WINETID. 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 (AS140469 isn't in the set, or no route object for AS140469 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 objectsAS140469 in itNot covered
AS-WINETID RADB 6122 Yes 1
ALTDB (also) 6122 Yes 1

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

  • Route object: none1
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
Route object: none2406:4940::/32No route object for it. Add a route object with origin AS140469 in the RIR database for the space.636 of 636
Route object: RIR103.153.190.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.153.191.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.153.190.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS140469 is announced.

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.