bgpreport

Network · data from 2026-11-12

AS136079 Universitas Amikom Yogyakarta

Registry name: IDNIC-AMIKOM-AS-ID - STMIK Amikom Yogyakarta, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136079, 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.
202.91.9.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 68
2405:2cc0:8::/48 Valid Nonecovered by 2405:2cc0::/32 636 100% 67
2405:2cc0:9::/48 Valid Nonecovered by 2405:2cc0::/32 636 100% 67
2405:2cc0::/48 Valid Other IRR onlyRADB 636 100% 69
2405:2cc0:1::/48 Valid Other IRR onlyRADB 636 100% 69
2405:2cc0:2::/48 Valid Other IRR onlyRADB 636 100% 69
2405:2cc0:3::/48 Valid Other IRR onlyRADB 636 100% 69
2405:2cc0:4::/48 Valid Other IRR onlyRADB 636 100% 69
2405:2cc0:5::/48 Valid Other IRR onlyRADB 636 100% 69
2405:2cc0:6::/48 Valid Other IRR onlyRADB 636 100% 69
2405:2cc0:7::/48 Valid Other IRR onlyRADB 636 100% 69
2405:2cc0:a::/48 Valid Other IRR onlyRADB 636 100% 69
2405:2cc0:b::/48 Valid Other IRR onlyRADB 636 100% 69
103.86.100.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.86.100.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.86.101.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
2405:2cc0::/32 Valid RIR databaseAPNIC, RADB 636 100% 69

AS-SET

AS136079'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 18 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR11
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none202.91.9.0/24No ROA covers it. Add a ROA for AS136079, maxLength 24.673 of 673
Route object: RIR202.91.9.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: none2405:2cc0:8::/48No route object for it. A route object for 2405:2cc0::/32 with origin AS136079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136079 in the RIR database for the space.636 of 636
Route object: none2405:2cc0:9::/48No route object for it. A route object for 2405:2cc0::/32 with origin AS136079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136079 in the RIR database for the space.636 of 636
Route object: RIR2405:2cc0::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2405:2cc0:1::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2405:2cc0:2::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2405:2cc0:3::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2405:2cc0:4::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2405:2cc0:5::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2405:2cc0:6::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2405:2cc0:7::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2405:2cc0:a::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2405:2cc0:b::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

2001:df0:5f00::/48RADBNo ROA
2405:2cc0:600d::/48APNIC, RADBValid
2405:2cc0:600e::/48APNICValid
2405:2cc0:600f::/48APNICValid

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.