bgpreport

Network · data from 2026-11-12

AS17810 VALUEFIRST-AS-AP - VALUEFIRST DIGITAL MEDIA PRIVATE LIMITED

Registry name: VALUEFIRST-AS-AP - VALUEFIRST DIGITAL MEDIA PRIVATE LIMITED, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17810, 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.212.73.0/24 No ROA RIR databaseAPNIC 672 100% 66
203.212.74.0/24 No ROA RIR databaseAPNIC 672 100% 66
103.229.250.0/23 No ROA RIR databaseAPNIC 671 100% 66
203.212.66.0/24 No ROA RIR databaseAPNIC 671 100% 66
203.212.68.0/24 No ROA RIR databaseAPNIC 671 100% 66
203.212.70.0/23 No ROA RIR databaseAPNIC 671 100% 66
203.212.67.0/24 Valid RIR databaseAPNIC 672 100% 67
203.212.69.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS17810 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: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none203.212.73.0/24No ROA covers it. Add a ROA for AS17810, maxLength 24.672 of 673
ROA: none203.212.74.0/24No ROA covers it. Add a ROA for AS17810, maxLength 24.672 of 673
ROA: none103.229.250.0/23No ROA covers it. Add a ROA for AS17810, maxLength 23.671 of 673
ROA: none203.212.66.0/24No ROA covers it. Add a ROA for AS17810, maxLength 24.671 of 673
ROA: none203.212.68.0/24No ROA covers it. Add a ROA for AS17810, maxLength 24.671 of 673
ROA: none203.212.70.0/23No ROA covers it. Add a ROA for AS17810, maxLength 23.671 of 673

Route objects not announced

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

103.229.2.0/23APNICNo ROA
203.212.64.0/22RADBNo ROA
203.212.64.0/23RADBNo ROA
203.212.64.0/24APNICNo ROA
203.212.65.0/24APNICNo ROA
203.212.68.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.