bgpreport

Network · data from 2026-11-12

AS132874 UMS-AS-AP - Universiti Malaysia Sabah

Registry name: UMS-AS-AP - Universiti Malaysia Sabah, MY · not in PeeringDB

5IPv4 routes 80.0% RPKI valid · 80.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.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
1Route objects not announced registered with origin AS132874, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS132874, 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.
103.26.196.0/23 Invalid: maxLength Nonecovered by 103.26.196.0/22 45 7%low visibility 29
103.26.196.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.26.197.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.26.198.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.26.199.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
2001:df4:6000::/48 Valid RIR databaseAPNIC, RADB 634 100% 68

AS-SET

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

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.26.196.0/23ROA 103.26.196.0/22 AS132874 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 103.26.196.0/23.45 of 673
Route object: none103.26.196.0/23No route object for it. A route object for 103.26.196.0/22 with origin AS132874 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132874 in the RIR database for the space.45 of 673

Route objects not announced

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

103.26.196.0/22APNIC, NTTCOM, RADBValid

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.