bgpreport

Network · data from 2026-11-12

AS134451 NME-INDONESIA-AS-AP - NewMedia Express Pte Ltd

Registry name: NME-INDONESIA-AS-AP - NewMedia Express Pte Ltd, ID · not in PeeringDB

8IPv4 routes 37.5% 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
5No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS134451, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134451, 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.200.7.0/24 No ROA Other IRR onlyRADB, REACH 673 100% 69
203.114.72.0/24 No ROA Other IRR onlyRADB, REACH 673 100% 69
203.114.74.0/24 No ROA Other IRR onlyRADB, REACH 673 100% 69
196.18.172.0/23 No ROA Other IRR onlyRADB 667 99% 69
104.250.105.0/24 No ROA RIR databaseARIN, NTTCOM, RADB, REACH 673 100% 69
45.114.118.0/24 Valid RIR databaseAPNIC, RADB, REACH 673 100% 69
103.60.9.0/24 Valid RIR databaseAPNIC, RADB, REACH 673 100% 69
172.111.158.0/24 Valid RIR databaseARIN 667 99% 66
2402:2f80:5::/48 Valid RIR databaseAPNIC, RADB 636 100% 70
2402:2f80:6::/48 Valid RIR databaseAPNIC, RADB 636 100% 70
2402:2f80:7::/48 Valid RIR databaseAPNIC, RADB 636 100% 70
2406:f400:120::/44 Valid RIR databaseAPNIC, RADB 635 100% 70

AS-SET

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

  • ROA: none5
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none103.200.7.0/24No ROA covers it. Add a ROA for AS134451, maxLength 24.673 of 673
Route object: RIR103.200.7.0/24Route object only in RADB, REACH. Add it in the RIR database for the space.673 of 673
ROA: none203.114.72.0/24No ROA covers it. Add a ROA for AS134451, maxLength 24.673 of 673
Route object: RIR203.114.72.0/24Route object only in RADB, REACH. Add it in the RIR database for the space.673 of 673
ROA: none203.114.74.0/24No ROA covers it. Add a ROA for AS134451, maxLength 24.673 of 673
Route object: RIR203.114.74.0/24Route object only in RADB, REACH. Add it in the RIR database for the space.673 of 673
ROA: none196.18.172.0/23No ROA covers it. Add a ROA for AS134451, maxLength 23.667 of 673
Route object: RIR196.18.172.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none104.250.105.0/24No ROA covers it. Add a ROA for AS134451, maxLength 24.673 of 673

Route objects not announced

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

103.55.9.0/24REACHInvalid: origin

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.