bgpreport

Network · data from 2026-11-12

AS38170 GTF-AS - Green Tree Frog

Registry name: GTF-AS - Green Tree Frog, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38170, 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.
202.3.32.0/21 No ROA Other origin onlycovered by 202.3.32.0/20 672 100% 67
202.3.36.0/23 No ROA Other origin onlycovered by 202.3.36.0/22 672 100% 67
202.3.39.0/24 No ROA Other origin onlycovered by 202.3.36.0/22 672 100% 67
203.15.244.0/24 No ROA Other origin only 672 100% 67
203.17.234.0/24 No ROA Other origin only 672 100% 67
203.30.90.0/23 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS38170 isn't in PeeringDB, where networks name their 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 23 are in fix.csv.

  • ROA: none5
  • Route object: none5
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none202.3.32.0/21No ROA covers it. Add a ROA for AS38170, maxLength 21.672 of 673
Route object: none202.3.32.0/21Route objects for it name AS7545, AS9627, AS24130. A route object for 202.3.32.0/20 with origin AS38170 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38170 in the RIR database for the space.672 of 673
ROA: none202.3.36.0/23No ROA covers it. Add a ROA for AS38170, maxLength 23.672 of 673
Route object: none202.3.36.0/23Route objects for it name AS9627. A route object for 202.3.36.0/22 with origin AS38170 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38170 in the RIR database for the space.672 of 673
ROA: none202.3.39.0/24No ROA covers it. Add a ROA for AS38170, maxLength 24.672 of 673
Route object: none202.3.39.0/24Route objects for it name AS9627. A route object for 202.3.36.0/22 with origin AS38170 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38170 in the RIR database for the space.672 of 673
ROA: none203.15.244.0/24No ROA covers it. Add a ROA for AS38170, maxLength 24.672 of 673
Route object: none203.15.244.0/24Route objects for it name AS7545, AS9627, AS24130. Add a route object with origin AS38170 in the RIR database for the space.672 of 673
ROA: none203.17.234.0/24No ROA covers it. Add a ROA for AS38170, maxLength 24.672 of 673
Route object: none203.17.234.0/24Route objects for it name AS2764, AS7545, AS24130. Add a route object with origin AS38170 in the RIR database for the space.672 of 673

Route objects not announced

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

202.3.32.0/20RADBNo ROA
202.3.32.0/24RADBNo ROA
202.3.33.0/24RADBNo ROA
202.3.34.0/24RADBNo ROA
202.3.35.0/24RADBNo ROA
202.3.36.0/22RADBNo ROA
202.3.36.0/24RADBNo ROA
202.3.56.0/23RADBNo ROA
202.3.57.0/24RADBNo ROA
203.12.136.0/24RADBNo ROA
203.16.167.0/24RADBNo ROA
210.10.122.0/23RADBNo ROA
210.11.200.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.