bgpreport

Network · data from 2026-11-12

AS139446 Gonet Teknologi Indonesia

Registry name: GONET-AS-ID - PT. Gonet Teknologi Indonesia, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS139446, 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.
2405:8440::/32 Invalid: origin None 5 1%low visibility 5
103.189.170.0/24 No ROA Other IRR onlyRADB 673 100% 70
103.189.171.0/24 No ROA Other IRR onlyRADB 668 99% 67
180.94.10.0/24 Valid Other IRR onlyRADB 673 100% 69
180.94.11.0/24 Valid Other IRR onlyRADB 673 100% 69
103.145.109.0/24 Valid RIR databaseAPNIC 673 100% 68
103.145.108.0/23 Valid RIR databaseAPNIC 672 100% 68
103.145.108.0/24 Valid RIR databaseAPNIC 672 100% 68

AS-SET

AS139446'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.

  • ROA: origin1
  • ROA: none2
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin2405:8440::/32An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS139446 should announce it, add a ROA for AS139446.5 of 636
Route object: none2405:8440::/32No route object for it. Add a route object with origin AS139446 in the RIR database for the space.5 of 636
ROA: none103.189.170.0/24No ROA covers it. Add a ROA for AS139446, maxLength 24.673 of 673
Route object: RIR103.189.170.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.189.171.0/24No ROA covers it. Add a ROA for AS139446, maxLength 24.668 of 673
Route object: RIR103.189.171.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR180.94.10.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR180.94.11.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

103.189.170.0/23RADBNo 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.