Network · data from 2026-11-12

AS45697 UBAYA-AS-ID - Universitas Surabaya

Registry name: UBAYA-AS-ID - Universitas Surabaya, ID · not in PeeringDB

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

2IPv6 routes 50.0% RPKI valid · 50.0% with a route object

1RPKI invalid 0 origin · 1 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 AS45697, seen from no peer

Announced routes

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


2001:df0:9a:8000::/49	Invalid: maxLength	Nonecovered by 2001:df0:9a::/48	7 1%low visibility	7
203.114.224.0/23	Valid	Other IRR onlyNTTCOM, RADB	673 100%	69
203.114.224.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	69
203.114.225.0/24	Valid	Other IRR onlyNTTCOM	673 100%	69
2001:df0:9a::/48	Valid	Other IRR onlyRADB	635 100%	70

2001:df0:9a:8000::/49

Invalid: maxLength

Nonecovered by 2001:df0:9a::/48

7 1%low visibility

203.114.224.0/23

Valid

Other IRR onlyNTTCOM, RADB

673 100%

203.114.224.0/24

Valid

Other IRR onlyNTTCOM, RADB

673 100%

203.114.225.0/24

Valid

Other IRR onlyNTTCOM

673 100%

2001:df0:9a::/48

Valid

Other IRR onlyRADB

635 100%

AS-SET

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

ROA: maxLength1
Route object: none1
Route object: RIR4

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	2001:df0:9a:8000::/49	ROA 2001:df0:9a::/48 AS45697 has maxLength 48; the route is a /49. Raise the maxLength, or add a ROA for 2001:df0:9a:8000::/49.	7 of 636
Route object: none	2001:df0:9a:8000::/49	No route object for it. A route object for 2001:df0:9a::/48 with origin AS45697 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS45697 in the RIR database for the space.	7 of 636
Route object: RIR	203.114.224.0/23	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	203.114.224.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	203.114.225.0/24	Route object only in NTTCOM. Add it in the RIR database for the space.	673 of 673
Route object: RIR	2001:df0:9a::/48	Route object only in RADB. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

2001:df0:9a:8000::/49

ROA 2001:df0:9a::/48 AS45697 has maxLength 48; the route is a /49. Raise the maxLength, or add a ROA for 2001:df0:9a:8000::/49.

7 of 636

Route object: none

2001:df0:9a:8000::/49

No route object for it. A route object for 2001:df0:9a::/48 with origin AS45697 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS45697 in the RIR database for the space.

7 of 636

Route object: RIR

203.114.224.0/23

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

673 of 673

Route object: RIR

203.114.224.0/24

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

673 of 673

Route object: RIR

203.114.225.0/24

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

673 of 673

Route object: RIR

2001:df0:9a::/48

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

635 of 636

Route objects not announced

Every route object with origin AS45697 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.