bgpreport

Network · data from 2026-11-12

AS58376 Angkasa Komunikasi Global Utama

Registry name: AKGU-AS-ID - PT Angkasa Komunikasi Global Utama, ID · PeeringDB

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

Announced routes

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

2403:e600:d00::/48 Invalid: maxLength Nonecovered by 2403:e600::/32 1 0%low visibility 1
2403:e600:f00::/48 Invalid: maxLength Nonecovered by 2403:e600::/32 1 0%low visibility 1
2403:e600:f04::/48 Invalid: maxLength Nonecovered by 2403:e600::/32 1 0%low visibility 1
2403:e600:fec::/48 Invalid: maxLength Nonecovered by 2403:e600::/32 1 0%low visibility 1
2403:e600::/32 Valid Other IRR onlyRADB 635 100% 70
43.245.188.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
43.245.188.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
43.245.191.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.29.148.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.29.148.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.29.149.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.29.150.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.29.151.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
212.117.56.0/21 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
212.117.59.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
212.117.60.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
212.117.61.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
212.117.62.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
212.117.63.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
43.245.189.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 669 99% 67
43.245.190.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 669 99% 67

AS-SET

PeeringDB's irr_as_set for AS58376: AS58376:AS-AKGTRANSIT. 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 (AS58376 isn't in the set, or no route object for AS58376 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 objectsAS58376 in itNot covered
AS58376:AS-AKGTRANSIT APNIC 8158 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 39 are in fix.csv.

  • ROA: maxLength4
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced30
ChangePrefix or setDetailFull-table peers
ROA: maxLength2403:e600:d00::/48ROA 2403:e600::/32 AS58376 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2403:e600:d00::/48.1 of 636
Route object: none2403:e600:d00::/48No route object for it. A route object for 2403:e600::/32 with origin AS58376 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58376 in the RIR database for the space.1 of 636
ROA: maxLength2403:e600:f00::/48ROA 2403:e600::/32 AS58376 has maxLength 32; ROA 2403:e600:f00::/40 AS58376 has maxLength 40; the route is a /48. Raise the maxLength, or add a ROA for 2403:e600:f00::/48.1 of 636
Route object: none2403:e600:f00::/48No route object for it. A route object for 2403:e600::/32 with origin AS58376 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58376 in the RIR database for the space.1 of 636
ROA: maxLength2403:e600:f04::/48ROA 2403:e600::/32 AS58376 has maxLength 32; ROA 2403:e600:f00::/40 AS58376 has maxLength 40; the route is a /48. Raise the maxLength, or add a ROA for 2403:e600:f04::/48.1 of 636
Route object: none2403:e600:f04::/48No route object for it. A route object for 2403:e600::/32 with origin AS58376 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58376 in the RIR database for the space.1 of 636
ROA: maxLength2403:e600:fec::/48ROA 2403:e600::/32 AS58376 has maxLength 32; ROA 2403:e600:f00::/40 AS58376 has maxLength 40; the route is a /48. Raise the maxLength, or add a ROA for 2403:e600:fec::/48.1 of 636
Route object: none2403:e600:fec::/48No route object for it. A route object for 2403:e600::/32 with origin AS58376 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58376 in the RIR database for the space.1 of 636
Route object: RIR2403:e600::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

43.245.188.0/23NTTCOM, RADBValid
43.245.190.0/23NTTCOM, RADBValid
103.29.148.0/23APNIC, NTTCOM, RADBValid
103.29.150.0/23APNIC, NTTCOM, RADBValid
103.29.186.0/24NTTCOMNo ROA
212.117.48.0/20RADBValid
212.117.48.0/21RADBValid
212.117.48.0/22RADBValid
212.117.48.0/23RADBValid
212.117.48.0/24RADBValid
212.117.49.0/24RADBValid
212.117.50.0/23RADBValid
212.117.50.0/24RADBValid
212.117.51.0/24RADBValid
212.117.52.0/22RADBValid
212.117.52.0/23RADBValid
212.117.52.0/24RADBValid
212.117.53.0/24RADBValid
212.117.54.0/23RADBValid
212.117.54.0/24RADBValid
212.117.55.0/24RADBValid
212.117.56.0/22APNIC, NTTCOM, RADBValid
212.117.56.0/23NTTCOM, RADBValid
212.117.56.0/24APNIC, NTTCOM, RADBValid
212.117.57.0/24APNIC, NTTCOM, RADBValid
212.117.58.0/23NTTCOM, RADBValid
212.117.58.0/24APNIC, NTTCOM, RADBValid
212.117.60.0/22APNIC, NTTCOM, RADBValid
212.117.60.0/23NTTCOM, RADBValid
212.117.62.0/23NTTCOM, RADBValid

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.