bgpreport

Network · data from 2026-11-12

AS59074 TAIKANG-INSURANCE-GROUP - TAIKANG INSURANCE GROUP CO.,LTD.

Registry name: TAIKANG-INSURANCE-GROUP - TAIKANG INSURANCE GROUP CO.,LTD., CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59074, 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.
2404:7240:6000::/48 Invalid: maxLength Nonecovered by 2404:7240::/32 99 16% 49
2404:7240::/33 Valid Nonecovered by 2404:7240::/32 636 100% 68
103.113.6.0/23 Valid Other IRR onlyRADB 673 100% 67
103.169.62.0/23 Valid Other IRR onlyRADB 673 100% 67
103.113.4.0/24 Valid Other IRR onlyRADB 672 100% 67
103.113.5.0/24 Valid Other IRR onlyRADB 672 100% 67
2404:7240:2008::/48 Valid Other IRR onlyRADB 636 100% 68

AS-SET

AS59074 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 14 are in fix.csv.

  • ROA: maxLength1
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: maxLength2404:7240:6000::/48ROA 2404:7240::/33 AS59074 has maxLength 33; the route is a /48. Raise the maxLength, or add a ROA for 2404:7240:6000::/48.99 of 636
Route object: none2404:7240:6000::/48No route object for it. A route object for 2404:7240::/32 with origin AS59074 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59074 in the RIR database for the space.99 of 636
Route object: none2404:7240::/33No route object for it. A route object for 2404:7240::/32 with origin AS59074 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59074 in the RIR database for the space.636 of 636
Route object: RIR103.113.6.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.169.62.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.113.4.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.113.5.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2404:7240:2008::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

103.227.48.0/24RADBNo ROA
103.227.49.0/24NTTCOM, RADBNo ROA
103.227.50.0/24NTTCOM, RADBNo ROA
103.227.51.0/24NTTCOM, RADBNo ROA
2404:7240::/32RADBNo ROA
2407:9bc0::/32RADBValid

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.