bgpreport

Network · data from 2026-11-12

AS140031 MYNUSA-ID - PT Mandala Lintas Nusa

Registry name: MYNUSA-ID - PT Mandala Lintas Nusa, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140031, 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.230.49.0/24 Valid Nonecovered by 103.230.48.0/23 673 100% 69
45.249.216.0/24 Valid Other IRR onlyRADB 673 100% 69
103.230.48.0/24 Valid Other IRR onlyRADB 673 100% 69
110.232.85.0/24 Valid Other IRR onlyRADB 673 100% 69
192.145.228.0/24 Valid Other IRR onlyRADB 673 100% 69
202.162.205.0/24 Valid Other IRR onlyRADB 673 100% 69
192.145.229.0/24 Valid Other IRR onlyRADB 671 100% 68

AS-SET

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

  • Route object: none1
  • Route object: RIR6
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none103.230.49.0/24No route object for it. A route object for 103.230.48.0/23 with origin AS140031 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140031 in the RIR database for the space.673 of 673
Route object: RIR45.249.216.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.230.48.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR110.232.85.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.145.228.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.162.205.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.145.229.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

45.249.216.0/23RADBNo ROA
103.230.48.0/23RADBValid
110.232.84.0/23RADBNo ROA
192.145.228.0/23RADBValid
202.162.204.0/23RADBNo ROA

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.