bgpreport

Network · data from 2026-11-12

AS138143 GERBANG AKSES INDONESIA

Registry name: GERBANGAKSES-AS-ID - PT GERBANG AKSES INDONESIA, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS138143, 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.
2404:6140::/35 Valid Nonecovered by 2404:6140::/32 635 100% 68
2404:6140:2000::/35 Valid Nonecovered by 2404:6140::/32 635 100% 68
2404:6140:4000::/35 Valid Nonecovered by 2404:6140::/32 635 100% 68
103.134.77.0/24 Valid Other IRR onlyRADB 673 100% 68
103.134.78.0/24 Valid Other IRR onlyRADB 673 100% 68
103.134.79.0/24 Valid Other IRR onlyRADB 673 100% 68
103.134.76.0/24 Valid Other IRR onlyRADB 672 100% 67

AS-SET

AS138143'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 9 are in fix.csv.

  • Route object: none3
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2404:6140::/35No route object for it. A route object for 2404:6140::/32 with origin AS138143 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138143 in the RIR database for the space.635 of 636
Route object: none2404:6140:2000::/35No route object for it. A route object for 2404:6140::/32 with origin AS138143 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138143 in the RIR database for the space.635 of 636
Route object: none2404:6140:4000::/35No route object for it. A route object for 2404:6140::/32 with origin AS138143 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138143 in the RIR database for the space.635 of 636
Route object: RIR103.134.77.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.134.78.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.134.79.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.134.76.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

103.134.76.0/22RADBNo ROA
2404:6140::/32RADBValid

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.