bgpreport

Network · data from 2026-11-12

AS10215 MICROLANDNET-AS-AP - Microland Limited. IT Infra Service Provider. India

Registry name: MICROLANDNET-AS-AP - Microland Limited. IT Infra Service Provider. India, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10215, 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.
203.90.5.0/24 No ROA Other origin onlycovered by 203.90.4.0/23 671 100% 66
203.31.8.0/24 No ROA Other IRR onlyRADB 671 100% 66
203.31.9.0/24 No ROA Other IRR onlyRADB 671 100% 67
103.104.70.0/24 No ROA RIR databaseAPNIC 672 100% 66
103.104.71.0/24 No ROA RIR databaseAPNIC 672 100% 66
203.17.31.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67
203.90.4.0/24 No ROA RIR databaseAPNIC 671 100% 66
103.104.70.0/23 No ROA RIR databaseAPNIC 2 0%low visibility 1
203.31.8.0/23 No ROA RIR databaseAPNIC, RADB 2 0%low visibility 2
203.90.4.0/23 No ROA RIR databaseAPNIC 2 0%low visibility 2

AS-SET

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

  • ROA: none10
  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none203.90.5.0/24No ROA covers it. Add a ROA for AS10215, maxLength 24.671 of 673
Route object: none203.90.5.0/24Route objects for it name AS7633. A route object for 203.90.4.0/23 with origin AS10215 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10215 in the RIR database for the space.671 of 673
ROA: none203.31.8.0/24No ROA covers it. Add a ROA for AS10215, maxLength 24.671 of 673
Route object: RIR203.31.8.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.31.9.0/24No ROA covers it. Add a ROA for AS10215, maxLength 24.671 of 673
Route object: RIR203.31.9.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.104.70.0/24No ROA covers it. Add a ROA for AS10215, maxLength 24.672 of 673
ROA: none103.104.71.0/24No ROA covers it. Add a ROA for AS10215, maxLength 24.672 of 673
ROA: none203.17.31.0/24No ROA covers it. Add a ROA for AS10215, maxLength 24.671 of 673
ROA: none203.90.4.0/24No ROA covers it. Add a ROA for AS10215, maxLength 24.671 of 673
ROA: none103.104.70.0/23No ROA covers it. Add a ROA for AS10215, maxLength 23.2 of 673
ROA: none203.31.8.0/23No ROA covers it. Add a ROA for AS10215, maxLength 23.2 of 673
ROA: none203.90.4.0/23No ROA covers it. Add a ROA for AS10215, maxLength 23.2 of 673

Route objects not announced

Every route object with origin AS10215 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.