bgpreport

Network · data from 2026-11-12

AS38767 Awan Media Semesta

Registry name: IDNIC-AMSCLOUD-AS-ID - PT Awan Media Semesta, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38767, 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.234.209.100/32 Invalid: maxLength Nonecovered by 103.234.209.0/24 0 0%low visibility 2
103.234.209.216/32 Invalid: maxLength Nonecovered by 103.234.209.0/24 0 0%low visibility 2
103.234.209.222/32 Invalid: maxLength Nonecovered by 103.234.209.0/24 0 0%low visibility 2
103.234.208.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.234.208.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.234.208.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.234.209.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.234.210.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.234.210.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.234.211.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
2001:df7:3c00::/48 Valid RIR databaseAPNIC, NTTCOM, RADB 34 5%low visibility 29

AS-SET

AS38767'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 6 are in fix.csv.

  • ROA: maxLength3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.234.209.100/32ROA 103.234.208.0/22 AS38767 has maxLength 22; ROA 103.234.208.0/23 AS38767 has maxLength 23; ROA 103.234.209.0/24 AS38767 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.234.209.100/32.0 of 673
Route object: none103.234.209.100/32No route object for it. A route object for 103.234.209.0/24 with origin AS38767 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38767 in the RIR database for the space.0 of 673
ROA: maxLength103.234.209.216/32ROA 103.234.208.0/22 AS38767 has maxLength 22; ROA 103.234.208.0/23 AS38767 has maxLength 23; ROA 103.234.209.0/24 AS38767 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.234.209.216/32.0 of 673
Route object: none103.234.209.216/32No route object for it. A route object for 103.234.209.0/24 with origin AS38767 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38767 in the RIR database for the space.0 of 673
ROA: maxLength103.234.209.222/32ROA 103.234.208.0/22 AS38767 has maxLength 22; ROA 103.234.208.0/23 AS38767 has maxLength 23; ROA 103.234.209.0/24 AS38767 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.234.209.222/32.0 of 673
Route object: none103.234.209.222/32No route object for it. A route object for 103.234.209.0/24 with origin AS38767 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38767 in the RIR database for the space.0 of 673

Route objects not announced

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