bgpreport

Network · data from 2026-11-12

AS58818 Universitas Muhammadiyah Yogyakarta

Registry name: IDNIC-UMY-AS-ID - Universitas Muhammadiyah Yogyakarta, ID · PeeringDB

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

Announced routes

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

2405:5fc0:8::/48 No ROA Other IRR onlyRADB 635 100% 67
2405:5fc0:d::/48 No ROA Other IRR onlyRADB 635 100% 67
2405:5fc0::/32 No ROA Other IRR onlyRADB 634 100% 67
2405:5fc0:3::/48 No ROA Other IRR onlyRADB 634 100% 67
2405:5fc0:5::/48 No ROA Other IRR onlyRADB 634 100% 67
2405:5fc0:6::/48 No ROA Other IRR onlyRADB 634 100% 67
2405:5fc0:7::/48 No ROA Other IRR onlyRADB 634 100% 67
2405:5fc0:9::/48 No ROA Other IRR onlyRADB 634 100% 67
2405:5fc0:b::/48 No ROA Other IRR onlyRADB 634 100% 67
2405:5fc0:f::/48 No ROA Other IRR onlyRADB 634 100% 67
103.251.180.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.251.180.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.251.181.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.251.182.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.251.183.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS58818: RS-SET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS58818 isn't in the set, or no route object for AS58818 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS58818 in itNot covered
RS-SET A route-set, not an AS-SET; route-sets aren't expanded.

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

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none2405:5fc0:8::/48No ROA covers it. Add a ROA for AS58818, maxLength 48.635 of 636
Route object: RIR2405:5fc0:8::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2405:5fc0:d::/48No ROA covers it. Add a ROA for AS58818, maxLength 48.635 of 636
Route object: RIR2405:5fc0:d::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2405:5fc0::/32No ROA covers it. Add a ROA for AS58818, maxLength 32.634 of 636
Route object: RIR2405:5fc0::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2405:5fc0:3::/48No ROA covers it. Add a ROA for AS58818, maxLength 48.634 of 636
Route object: RIR2405:5fc0:3::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2405:5fc0:5::/48No ROA covers it. Add a ROA for AS58818, maxLength 48.634 of 636
Route object: RIR2405:5fc0:5::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2405:5fc0:6::/48No ROA covers it. Add a ROA for AS58818, maxLength 48.634 of 636
Route object: RIR2405:5fc0:6::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2405:5fc0:7::/48No ROA covers it. Add a ROA for AS58818, maxLength 48.634 of 636
Route object: RIR2405:5fc0:7::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2405:5fc0:9::/48No ROA covers it. Add a ROA for AS58818, maxLength 48.634 of 636
Route object: RIR2405:5fc0:9::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2405:5fc0:b::/48No ROA covers it. Add a ROA for AS58818, maxLength 48.634 of 636
Route object: RIR2405:5fc0:b::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2405:5fc0:f::/48No ROA covers it. Add a ROA for AS58818, maxLength 48.634 of 636
Route object: RIR2405:5fc0:f::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

103.251.180.0/23APNIC, NTTCOMValid
103.251.182.0/23APNIC, NTTCOMValid
2405:5fc0::/48RADBNo ROA
2405:5fc0:1::/48RADBNo ROA
2405:5fc0:4::/48RADBNo ROA
2405:5fc0:a::/48RADBNo ROA
2405:5fc0:c::/48RADBNo ROA
2405:5fc0:e::/48RADBNo ROA
2405:5fc0:10::/48RADBNo ROA
2405:5fc0:11::/48RADBNo ROA
2405:5fc0:12::/48RADBNo 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.