bgpreport

Network · data from 2026-11-12

AS138292 GALAXY01-AS - Galaxy Digitech India Private Limited

Registry name: GALAXY01-AS - Galaxy Digitech India Private Limited, IN · not in PeeringDB

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

Announced routes

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

103.122.228.0/24 No ROA RIR databaseAPNIC 672 100% 66
103.122.230.0/24 No ROA RIR databaseAPNIC 672 100% 66
103.122.231.0/24 No ROA RIR databaseAPNIC 672 100% 66

AS-SET

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

  • ROA: none3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none103.122.228.0/24No ROA covers it. Add a ROA for AS138292, maxLength 24.672 of 673
ROA: none103.122.230.0/24No ROA covers it. Add a ROA for AS138292, maxLength 24.672 of 673
ROA: none103.122.231.0/24No ROA covers it. Add a ROA for AS138292, maxLength 24.672 of 673

Route objects not announced

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

103.122.228.0/22APNICNo ROA
103.122.228.0/23APNICNo ROA
103.122.229.0/24APNICNo ROA
103.122.230.0/23APNICNo 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.