bgpreport

Network · data from 2026-11-12

AS17753 DATAINGENIOUS-AS-AP - DATA INGENIOUS GLOBAL LIMITED

Registry name: DATAINGENIOUS-AS-AP - DATA INGENIOUS GLOBAL LIMITED, IN · not in PeeringDB

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

Announced routes

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

202.157.81.0/24 No ROA Other origin onlycovered by 202.157.80.0/23 672 100% 66
2402:8c00:2::/48 No ROA None 631 99% 68
2402:8c00:9::/48 No ROA None 631 99% 68
202.157.64.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.157.67.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.157.82.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.157.85.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.157.88.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.157.89.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.157.90.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.157.91.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.157.93.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.157.95.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.157.68.0/24 No ROA RIR databaseAPNIC 672 100% 66
202.157.69.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 66
202.157.70.0/24 No ROA RIR databaseAPNIC 672 100% 66
202.157.71.0/24 No ROA RIR databaseAPNIC 672 100% 66
202.157.73.0/24 No ROA RIR databaseAPNIC 672 100% 66
202.157.74.0/24 No ROA RIR databaseAPNIC 672 100% 66
202.157.76.0/24 No ROA RIR databaseAPNIC 672 100% 66
202.157.77.0/24 No ROA RIR databaseAPNIC 672 100% 66
202.157.78.0/24 No ROA RIR databaseAPNIC 672 100% 66
202.157.79.0/24 No ROA RIR databaseAPNIC 672 100% 66
202.157.83.0/24 No ROA RIR databaseAPNIC 672 100% 66
202.157.87.0/24 No ROA RIR databaseAPNIC 672 100% 66
202.157.72.0/24 No ROA RIR databaseAPNIC 671 100% 66
202.157.94.0/24 No ROA RIR databaseAPNIC 641 95% 66

AS-SET

AS17753 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 39 are in fix.csv.

  • ROA: none27
  • Route object: none3
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none202.157.81.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
Route object: none202.157.81.0/24Route objects for it name AS9498. A route object for 202.157.80.0/23 with origin AS17753 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17753 in the RIR database for the space.672 of 673
ROA: none2402:8c00:2::/48No ROA covers it. Add a ROA for AS17753, maxLength 48.631 of 636
Route object: none2402:8c00:2::/48No route object for it. Add a route object with origin AS17753 in the RIR database for the space.631 of 636
ROA: none2402:8c00:9::/48No ROA covers it. Add a ROA for AS17753, maxLength 48.631 of 636
Route object: none2402:8c00:9::/48No route object for it. Add a route object with origin AS17753 in the RIR database for the space.631 of 636
ROA: none202.157.64.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.673 of 673
ROA: none202.157.67.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.673 of 673
ROA: none202.157.82.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.673 of 673
ROA: none202.157.85.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.673 of 673
ROA: none202.157.88.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.673 of 673
ROA: none202.157.89.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.673 of 673
ROA: none202.157.90.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.673 of 673
ROA: none202.157.91.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.673 of 673
ROA: none202.157.93.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.673 of 673
ROA: none202.157.95.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.673 of 673
ROA: none202.157.68.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
ROA: none202.157.69.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
ROA: none202.157.70.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
ROA: none202.157.71.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
ROA: none202.157.73.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
ROA: none202.157.74.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
ROA: none202.157.76.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
ROA: none202.157.77.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
ROA: none202.157.78.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
ROA: none202.157.79.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
ROA: none202.157.83.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
ROA: none202.157.87.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.672 of 673
ROA: none202.157.72.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.671 of 673
ROA: none202.157.94.0/24No ROA covers it. Add a ROA for AS17753, maxLength 24.641 of 673

Route objects not announced

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

202.157.64.0/19RADBNo ROA
202.157.65.0/24APNICNo ROA
202.157.66.0/24APNICNo ROA
202.157.75.0/24APNICNo ROA
202.157.80.0/23APNICNo ROA
202.157.80.0/24APNICNo ROA
202.157.84.0/24APNICNo ROA
202.157.86.0/24APNICNo ROA
202.157.92.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.