bgpreport

Network · data from 2026-11-12

AS64088 BIOCLINICA-AS-AP - ioClinica India Private Limited

Registry name: BIOCLINICA-AS-AP - ioClinica India Private Limited, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS64088, 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.209.110.0/24 No ROA RIR databaseAPNIC 673 100% 67
103.76.206.0/24 Valid RIR databaseAPNIC 672 100% 67
103.76.207.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

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

  • ROA: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none103.209.110.0/24No ROA covers it. Add a ROA for AS64088, maxLength 24.673 of 673

Route objects not announced

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

103.209.111.0/24APNICNo 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.