bgpreport

Network · data from 2026-11-12

AS150270 PT Mahkota Mas Insan Persada

Registry name: IDNIC-MAHKOTAMAS-AS-ID - PT Mahkota Mas Insan Persada, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS150270, 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.39.69.0/24 Invalid: origin Other origin only 4 1%low visibility 3
103.39.68.0/23 Invalid: origin Other origin only 3 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS150270: AS-DARTMEDIA. 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 (AS150270 isn't in the set, or no route object for AS150270 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 objectsAS150270 in itNot covered
AS-DARTMEDIA In no IRR database read today.

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

  • ROA: origin2
  • Route object: none2
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: origin103.39.69.0/24ROAs covering it name AS140443, not AS150270. If AS150270 should announce it, add a ROA for AS150270.4 of 673
Route object: none103.39.69.0/24Route objects for it name AS140443. Add a route object with origin AS150270 in the RIR database for the space.4 of 673
ROA: origin103.39.68.0/23ROAs covering it name AS140443, not AS150270. If AS150270 should announce it, add a ROA for AS150270.3 of 673
Route object: none103.39.68.0/23Route objects for it name AS140443. Add a route object with origin AS150270 in the RIR database for the space.3 of 673
AS-SET: not foundAS-DARTMEDIAPeeringDB names AS-DARTMEDIA; no IRR database read has it.

Route objects not announced

Every route object with origin AS150270 is announced.

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.