bgpreport

Network · data from 2026-11-12

AS55684 Universitas Sebelas Maret

Registry name: UNS-AS-ID - Universitas Sebelas Maret, ID · PeeringDB

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

Announced routes

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

203.6.148.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 69
203.6.149.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 69
203.6.148.0/23 No ROA Other IRR onlyRADB 18 3%low visibility 18
103.23.224.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.23.225.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.23.226.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.23.227.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.23.224.0/22 Valid RIR databaseAPNIC, RADB 18 3%low visibility 18

AS-SET

AS55684'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 10 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none203.6.148.0/24No ROA covers it. Add a ROA for AS55684, maxLength 24.672 of 673
Route object: RIR203.6.148.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.6.149.0/24No ROA covers it. Add a ROA for AS55684, maxLength 24.672 of 673
Route object: RIR203.6.149.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.6.148.0/23No ROA covers it. Add a ROA for AS55684, maxLength 23.18 of 673
Route object: RIR203.6.148.0/23Route object only in RADB. Add it in the RIR database for the space.18 of 673

Route objects not announced

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

103.23.224.0/23APNIC, RADBValid
103.23.226.0/23APNIC, RADBValid
2001:df0:220::/48RADBNo ROA
2401:90e0::/32RADBNo ROA

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.