Network · data from 2026-11-12

AS269796 AS269796 - JIREH WAN SAS

Registry name: AS269796 - JIREH WAN SAS, CO · not in PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

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

1Route objects not announced registered with origin AS269796, seen from no peer

Announced routes

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


45.185.31.0/24	Valid	Other IRR onlyRADB	668 99%	67

45.185.31.0/24

Valid

Other IRR onlyRADB

668 99%

AS-SET

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

Route object: RIR1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.185.31.0/24	Route object only in RADB. Add it in the RIR database for the space.	668 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.185.31.0/24

Route object only in RADB. Add it in the RIR database for the space.

668 of 673

Route objects not announced

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


2803:f360::/32	RADB	Valid

2803:f360::/32

RADB

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.