Network · data from 2026-11-12

AS199592 WAHYU WAHYU

Registry name: WAHYU WAHYU, ID · PeeringDB

5IPv4 routes 80.0% RPKI valid · 80.0% with a route object

6IPv6 routes 100.0% RPKI valid · 100.0% with a route object

1RPKI invalid 1 origin · 0 maxLength

0No ROA 1 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

4Route objects not announced registered with origin AS199592, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS199592, 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.


194.242.130.0/23	Invalid: origin	Other origin only	2 0%low visibility	2
109.65.30.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
155.117.1.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
169.40.55.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
155.117.182.0/24	Valid	RIR databaseRADB, RIPE	669 99%	68
2a10:fa83:a000::/36	Valid	RIR databaseRIPE	636 100%	69
2a14:7580:e800::/40	Valid	RIR databaseRIPE	636 100%	69
2a10:fa83:4000::/36	Valid	RIR databaseRIPE	634 100%	69
2a10:fa83:7000::/36	Valid	RIR databaseRIPE	633 100%	67
2a10:fa83:3000::/36	Valid	RIR databaseRIPE	632 99%	67
2a10:fa83:2000::/36	Valid	RIR databaseRIPE	631 99%	67

194.242.130.0/23

Invalid: origin

Other origin only

2 0%low visibility

109.65.30.0/24

Valid

RIR databaseRADB, RIPE

671 100%

155.117.1.0/24

Valid

RIR databaseRADB, RIPE

671 100%

169.40.55.0/24

Valid

RIR databaseRADB, RIPE

671 100%

155.117.182.0/24

Valid

RIR databaseRADB, RIPE

669 99%

2a10:fa83:a000::/36

Valid

RIR databaseRIPE

636 100%

2a14:7580:e800::/40

Valid

RIR databaseRIPE

636 100%

2a10:fa83:4000::/36

Valid

RIR databaseRIPE

634 100%

2a10:fa83:7000::/36

Valid

RIR databaseRIPE

633 100%

2a10:fa83:3000::/36

Valid

RIR databaseRIPE

632 99%

2a10:fa83:2000::/36

Valid

RIR databaseRIPE

631 99%

AS-SET

AS199592's PeeringDB record names no 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 6 are in fix.csv.

ROA: origin1
Route object: none1
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
ROA: origin	194.242.130.0/23	ROAs covering it name AS834, not AS199592. If AS199592 should announce it, add a ROA for AS199592.	2 of 673
Route object: none	194.242.130.0/23	Route objects for it name AS834, AS3257. Add a route object with origin AS199592 in the RIR database for the space.	2 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

194.242.130.0/23

ROAs covering it name AS834, not AS199592. If AS199592 should announce it, add a ROA for AS199592.

2 of 673

Route object: none

194.242.130.0/23

Route objects for it name AS834, AS3257. Add a route object with origin AS199592 in the RIR database for the space.

2 of 673

Route objects not announced

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


79.182.50.0/24	RADB, RIPE	Valid
2a10:fa83::/32	RIPE	Valid
2a14:67c1:500::/40	RIPE	Valid
2a14:67c1:600::/40	RIPE	Valid

79.182.50.0/24

RADB, RIPE

Valid

2a10:fa83::/32

RIPE

Valid

2a14:67c1:500::/40

RIPE

Valid

2a14:67c1:600::/40

RIPE

Valid

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.