bgpreport

Network · data from 2026-11-12

AS24514 Malaysian Research & Education Network (MYREN)

Registry name: MYREN-MY - MINISTRY OF HIGHER EDUCATION MALAYSIA, MY · PeeringDB

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

Announced routes

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

122.129.120.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
122.129.124.0/24 Valid RIR databaseAPNIC 672 100% 68
122.129.125.0/24 Valid RIR databaseAPNIC, NTTCOM 672 100% 68
122.129.126.0/24 Valid RIR databaseAPNIC, NTTCOM 672 100% 68
122.129.127.0/24 Valid RIR databaseAPNIC, NTTCOM 672 100% 68
203.80.20.0/24 Valid RIR databaseAPNIC 672 100% 68
203.80.21.0/24 Valid RIR databaseAPNIC 672 100% 68
203.80.22.0/24 Valid RIR databaseAPNIC 672 100% 68
203.80.23.0/24 Valid RIR databaseAPNIC 672 100% 68
103.26.74.0/23 Valid RIR databaseAPNIC, RADB 671 100% 69
122.129.124.0/22 Valid RIR databaseAPNIC, RADB 671 100% 69
150.129.184.0/23 Valid RIR databaseAPNIC, RADB 671 100% 69
203.80.16.0/22 Valid RIR databaseAPNIC, RADB 671 100% 69
203.80.20.0/22 Valid RIR databaseAPNIC, RADB 671 100% 69
103.17.78.0/24 Valid RIR databaseAPNIC 669 99% 69
103.26.47.0/24 Valid RIR databaseAPNIC 669 99% 69
103.26.74.0/24 Valid RIR databaseAPNIC 669 99% 69
122.129.120.0/24 Valid RIR databaseAPNIC 669 99% 69
122.129.121.0/24 Valid RIR databaseAPNIC 669 99% 69
122.129.122.0/24 Valid RIR databaseAPNIC 669 99% 69
122.129.123.0/24 Valid RIR databaseAPNIC 669 99% 69
150.129.185.0/24 Valid RIR databaseAPNIC 669 99% 69
150.129.186.0/24 Valid RIR databaseAPNIC 669 99% 69
203.80.16.0/24 Valid RIR databaseAPNIC 669 99% 69
203.80.19.0/24 Valid RIR databaseAPNIC 669 99% 69
2404:a8:4000::/36 Valid RIR databaseAPNIC, RADB 636 100% 68
2404:a8:5::/48 Valid RIR databaseAPNIC 635 100% 68
2404:a8:19::/48 Valid RIR databaseAPNIC 635 100% 68
2404:a8:3ff::/48 Valid RIR databaseAPNIC 635 100% 68

AS-SET

PeeringDB's irr_as_set for AS24514: AS24514:AS-MYREN. 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 (AS24514 isn't in the set, or no route object for AS24514 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 objectsAS24514 in itNot covered
AS24514:AS-MYREN APNIC 211359 Yes 0

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

  • Route object: not announced14

Route objects not announced

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

103.26.75.0/24APNICInvalid: maxLength
103.127.51.0/24APNICValid
122.129.120.0/21NTTCOM, RADBNo ROA
150.129.184.0/24APNICInvalid: maxLength
150.129.187.0/24APNICNo ROA
203.80.16.0/21NTTCOM, RADBNo ROA
203.80.17.0/24APNICInvalid: maxLength
203.80.18.0/24APNICInvalid: maxLength
2001:df0:427::/48APNICInvalid: origin
2404:a8::/32RADBNo ROA
2404:a8:10::/48APNICNo ROA
2404:a8:163::/48APNICNo ROA
2404:a8:400b::/48APNICInvalid: maxLength
2404:a8:4094::/48APNICInvalid: maxLength

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.