Network · data from 2026-11-12

AS18120 GEMINI-AS-IN - Gemini Software Solutions (P) Ltd. Hosting Services, India

Registry name: GEMINI-AS-IN - Gemini Software Solutions (P) Ltd. Hosting Services, India, IN · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 50.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

4No ROA 2 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS18120, seen from no peer

Announced routes

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


110.232.180.0/23	No ROA	Nonecovered by 110.232.180.0/22	673 100%	66
202.72.248.0/23	No ROA	Nonecovered by 202.72.248.0/22	672 100%	67
110.232.180.0/22	No ROA	RIR databaseAPNIC	673 100%	66
202.72.248.0/22	No ROA	RIR databaseAPNIC	672 100%	67

AS-SET

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

ROA: none4
Route object: none2

Change	Prefix or set	Detail	Full-table peers
ROA: none	110.232.180.0/23	No ROA covers it. Add a ROA for AS18120, maxLength 23.	673 of 673
Route object: none	110.232.180.0/23	No route object for it. A route object for 110.232.180.0/22 with origin AS18120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18120 in the RIR database for the space.	673 of 673
ROA: none	202.72.248.0/23	No ROA covers it. Add a ROA for AS18120, maxLength 23.	672 of 673
Route object: none	202.72.248.0/23	No route object for it. A route object for 202.72.248.0/22 with origin AS18120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18120 in the RIR database for the space.	672 of 673
ROA: none	110.232.180.0/22	No ROA covers it. Add a ROA for AS18120, maxLength 22.	673 of 673
ROA: none	202.72.248.0/22	No ROA covers it. Add a ROA for AS18120, maxLength 22.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

110.232.180.0/23

No ROA covers it. Add a ROA for AS18120, maxLength 23.

673 of 673

Route object: none

110.232.180.0/23

No route object for it. A route object for 110.232.180.0/22 with origin AS18120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18120 in the RIR database for the space.

673 of 673

ROA: none

202.72.248.0/23

No ROA covers it. Add a ROA for AS18120, maxLength 23.

672 of 673

Route object: none

202.72.248.0/23

No route object for it. A route object for 202.72.248.0/22 with origin AS18120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18120 in the RIR database for the space.

672 of 673

ROA: none

110.232.180.0/22

No ROA covers it. Add a ROA for AS18120, maxLength 22.

673 of 673

ROA: none

202.72.248.0/22

No ROA covers it. Add a ROA for AS18120, maxLength 22.

672 of 673

Route objects not announced

Every route object with origin AS18120 is announced.

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.