bgpreport

Network · data from 2026-11-12

AS142373 Multi Network Indonesia

Registry name: IDNIC-MULTINET-AS-ID - PT Multi Network Indonesia, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS142373, 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.
2401:c7a0::/34 Valid Nonecovered by 2401:c7a0::/32 635 100% 69
2401:c7a0:4000::/34 Valid Nonecovered by 2401:c7a0::/32 635 100% 69
2401:c7a0:8000::/34 Valid Nonecovered by 2401:c7a0::/32 635 100% 69
2401:c7a0:c000::/34 Valid Nonecovered by 2401:c7a0::/32 635 100% 69
103.171.82.0/23 Valid RIR databaseAPNIC, RADB 673 100% 68
103.171.82.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.171.83.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
2401:c7a0::/32 Valid RIR databaseAPNIC, RADB 635 100% 69
2401:c7a0:fffa::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2401:c7a0:fffc::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2401:c7a0:fffd::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2401:c7a0:fffe::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2401:c7a0:ffff::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2401:c7a0:fffb::/48 Valid RIR databaseAPNIC, RADB 34 5%low visibility 28

AS-SET

PeeringDB's irr_as_set for AS142373: AS142373:AS-CUST-MNI. 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 (AS142373 isn't in the set, or no route object for AS142373 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 objectsAS142373 in itNot covered
AS142373:AS-CUST-MNI APNIC 331113 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 4 are in fix.csv.

  • Route object: none4
ChangePrefix or setDetailFull-table peers
Route object: none2401:c7a0::/34No route object for it. A route object for 2401:c7a0::/32 with origin AS142373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS142373 in the RIR database for the space.635 of 636
Route object: none2401:c7a0:4000::/34No route object for it. A route object for 2401:c7a0::/32 with origin AS142373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS142373 in the RIR database for the space.635 of 636
Route object: none2401:c7a0:8000::/34No route object for it. A route object for 2401:c7a0::/32 with origin AS142373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS142373 in the RIR database for the space.635 of 636
Route object: none2401:c7a0:c000::/34No route object for it. A route object for 2401:c7a0::/32 with origin AS142373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS142373 in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS142373 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.