bgpreport

Network · data from 2026-11-12

AS63501 Mega Mentari Mandiri

Registry name: MEGAHUB-AS-ID - PT Mega Mentari Mandiri, ID · PeeringDB

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

Announced routes

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

141.92.64.0/19 No ROA Other origin only 672 100% 67
2403:fc80::/32 Valid None 634 100% 69
61.14.248.0/23 Valid Other IRR onlyRADB 673 100% 69
103.39.48.0/23 Valid Other IRR onlyRADB 673 100% 69
103.39.50.0/23 Valid Other IRR onlyRADB 673 100% 69
103.39.50.0/24 Valid Other IRR onlyRADB 673 100% 69
103.39.48.0/24 Valid Other IRR onlyRADB 36 5%low visibility 30
103.39.49.0/24 Valid Other IRR onlyRADB 36 5%low visibility 30
103.39.51.0/24 Valid Other IRR onlyRADB 36 5%low visibility 30
61.14.248.0/24 Valid RIR databaseAPNIC, RADB 217 32% 58

AS-SET

PeeringDB's irr_as_set for AS63501: AS63501. 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 (AS63501 isn't in the set, or no route object for AS63501 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 objectsAS63501 in itNot covered
AS63501 A single AS number, not a set: AS63501 (this network), 16 route objects.

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: RIR7
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none141.92.64.0/19No ROA covers it. Add a ROA for AS63501, maxLength 19.672 of 673
Route object: none141.92.64.0/19Route objects for it name AS8435. Add a route object with origin AS63501 in the RIR database for the space.672 of 673
Route object: none2403:fc80::/32No route object for it. Add a route object with origin AS63501 in the RIR database for the space.634 of 636
Route object: RIR61.14.248.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.39.48.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.39.50.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.39.50.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.39.48.0/24Route object only in RADB. Add it in the RIR database for the space.36 of 673
Route object: RIR103.39.49.0/24Route object only in RADB. Add it in the RIR database for the space.36 of 673
Route object: RIR103.39.51.0/24Route object only in RADB. Add it in the RIR database for the space.36 of 673

Route objects not announced

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

61.14.248.0/22APNIC, RADBValid
61.14.249.0/24APNIC, RADBValid
61.14.250.0/23RADBValid
61.14.250.0/24APNIC, RADBValid
61.14.251.0/24APNIC, RADBValid
103.6.180.0/24APNICNo ROA
103.16.197.0/24APNICNo ROA
103.39.48.0/22APNIC, 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.