bgpreport

Network · data from 2026-11-12

AS138841 Media Andalan Nusa

Registry name: GROOVY-AS-ID - PT Media Andalan Nusa, ID · PeeringDB

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

Announced routes

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

43.229.252.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68

AS-SET

AS138841's PeeringDB record names no 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 26 are in fix.csv.

  • Route object: not announced26

Route objects not announced

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

103.75.168.0/24RADBNo ROA
103.75.169.0/24RADBNo ROA
103.75.170.0/24RADBNo ROA
103.214.120.0/24RADBNo ROA
103.214.121.0/24RADBNo ROA
103.238.136.0/24RADBNo ROA
110.232.73.0/24RADBValid
110.232.74.0/24RADBValid
110.232.75.0/24RADBValid
110.232.76.0/24RADBValid
110.232.77.0/24RADBValid
110.232.79.0/24APNIC, RADBValid
110.232.88.0/24RADBValid
110.232.89.0/24RADBValid
116.206.4.0/22RADBNo ROA
150.107.138.0/24RADBValid
150.107.139.0/24RADBValid
150.107.148.0/24RADBNo ROA
150.107.149.0/24RADBNo ROA
150.107.150.0/24RADBNo ROA
150.107.151.0/24RADBNo ROA
202.162.200.0/24RADBValid
202.162.201.0/24RADBValid
202.162.206.0/24RADBValid
202.162.207.0/24RADBValid
2405:2e40::/36APNICNo 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.