bgpreport

Network · data from 2026-11-12

AS38044 GITN-NETWORK - GITN-NETWORK

Registry name: GITN-NETWORK - GITN-NETWORK, MY · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38044, 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.60.57.0/24 No ROA Nonecovered by 202.60.56.0/22 673 100% 66
202.60.59.0/24 No ROA Nonecovered by 202.60.56.0/22 673 100% 66
2400:7400::/33 No ROA Nonecovered by 2400:7400::/32 636 100% 67
2400:7400:8000::/33 No ROA Nonecovered by 2400:7400::/32 636 100% 67
175.28.12.0/22 No ROA Other IRR onlyRADB 671 100% 66
202.60.56.0/22 No ROA Other IRR onlyRADB 671 100% 68
203.12.220.0/24 No ROA Other IRR onlyRADB 671 100% 66
203.62.1.0/24 No ROA Other IRR onlyRADB 671 100% 66
43.252.232.0/22 No ROA RIR databaseAPNIC, RADB 671 100% 66
43.252.233.0/24 No ROA RIR databaseAPNIC 671 100% 66
43.252.235.0/24 No ROA RIR databaseAPNIC 671 100% 66
103.245.88.0/22 No ROA RIR databaseAPNIC, RADB 671 100% 66

AS-SET

AS38044 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 29 are in fix.csv.

  • ROA: none12
  • Route object: none4
  • Route object: RIR4
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none202.60.57.0/24No ROA covers it. Add a ROA for AS38044, maxLength 24.673 of 673
Route object: none202.60.57.0/24No route object for it. A route object for 202.60.56.0/22 with origin AS38044 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38044 in the RIR database for the space.673 of 673
ROA: none202.60.59.0/24No ROA covers it. Add a ROA for AS38044, maxLength 24.673 of 673
Route object: none202.60.59.0/24No route object for it. A route object for 202.60.56.0/22 with origin AS38044 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38044 in the RIR database for the space.673 of 673
ROA: none2400:7400::/33No ROA covers it. Add a ROA for AS38044, maxLength 33.636 of 636
Route object: none2400:7400::/33No route object for it. A route object for 2400:7400::/32 with origin AS38044 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38044 in the RIR database for the space.636 of 636
ROA: none2400:7400:8000::/33No ROA covers it. Add a ROA for AS38044, maxLength 33.636 of 636
Route object: none2400:7400:8000::/33No route object for it. A route object for 2400:7400::/32 with origin AS38044 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38044 in the RIR database for the space.636 of 636
ROA: none175.28.12.0/22No ROA covers it. Add a ROA for AS38044, maxLength 22.671 of 673
Route object: RIR175.28.12.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.60.56.0/22No ROA covers it. Add a ROA for AS38044, maxLength 22.671 of 673
Route object: RIR202.60.56.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.12.220.0/24No ROA covers it. Add a ROA for AS38044, maxLength 24.671 of 673
Route object: RIR203.12.220.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.62.1.0/24No ROA covers it. Add a ROA for AS38044, maxLength 24.671 of 673
Route object: RIR203.62.1.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none43.252.232.0/22No ROA covers it. Add a ROA for AS38044, maxLength 22.671 of 673
ROA: none43.252.233.0/24No ROA covers it. Add a ROA for AS38044, maxLength 24.671 of 673
ROA: none43.252.235.0/24No ROA covers it. Add a ROA for AS38044, maxLength 24.671 of 673
ROA: none103.245.88.0/22No ROA covers it. Add a ROA for AS38044, maxLength 22.671 of 673

Route objects not announced

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

103.245.88.0/23RADBNo ROA
103.245.88.0/24RADBNo ROA
103.245.89.0/24RADBNo ROA
103.245.90.0/23RADBNo ROA
103.245.90.0/24RADBNo ROA
103.245.91.0/24RADBNo ROA
2400:7400::/32RADBNo ROA
2400:7400:32::/48RADBNo ROA
2402:4640:8000::/33APNICNo 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.