bgpreport

Network · data from 2026-11-12

AS56202 RIA-INFOSOLUTIONS-IN - Suite no 10, Level 5; C Wing

Registry name: RIA-INFOSOLUTIONS-IN - Suite no 10, Level 5; C Wing, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56202, 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.251.20.0/24 No ROA Other origin only 673 100% 67
103.251.21.0/24 No ROA Other origin only 673 100% 67
103.247.149.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.38.172.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.38.173.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.38.174.0/24 No ROA RIR databaseAPNIC 673 100% 66

AS-SET

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

  • ROA: none6
  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none103.251.20.0/24No ROA covers it. Add a ROA for AS56202, maxLength 24.673 of 673
Route object: none103.251.20.0/24Route objects for it name AS132940. Add a route object with origin AS56202 in the RIR database for the space.673 of 673
ROA: none103.251.21.0/24No ROA covers it. Add a ROA for AS56202, maxLength 24.673 of 673
Route object: none103.251.21.0/24Route objects for it name AS4755, AS132940. Add a route object with origin AS56202 in the RIR database for the space.673 of 673
ROA: none103.247.149.0/24No ROA covers it. Add a ROA for AS56202, maxLength 24.673 of 673
ROA: none202.38.172.0/24No ROA covers it. Add a ROA for AS56202, maxLength 24.673 of 673
ROA: none202.38.173.0/24No ROA covers it. Add a ROA for AS56202, maxLength 24.673 of 673
ROA: none202.38.174.0/24No ROA covers it. Add a ROA for AS56202, maxLength 24.673 of 673

Route objects not announced

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

103.247.148.0/24APNICValid
103.247.150.0/24APNICValid
202.38.172.0/22RADBNo ROA
2400:5700::/32RADBNo 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.