bgpreport

Network · data from 2026-11-12

AS138457 CAICT-AS-AP - China Academy of Information and Communications Technology

Registry name: CAICT-AS-AP - China Academy of Information and Communications Technology, CN · not in PeeringDB

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

Announced routes

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

2402:7d80::/48 Valid Other origin onlycovered by 2402:7d80::/32 9 1%low visibility 5
2402:7d80:8888::/48 Valid Other origin onlycovered by 2402:7d80::/32 9 1%low visibility 5
45.120.243.0/24 Valid RIR databaseAPNIC 671 100% 67
103.61.60.0/24 Valid RIR databaseAPNIC 363 54% 60
103.61.61.0/24 Valid RIR databaseAPNIC 13 2%low visibility 9
103.61.62.0/24 Valid RIR databaseAPNIC 13 2%low visibility 9
103.61.63.0/24 Valid RIR databaseAPNIC 13 2%low visibility 9

AS-SET

AS138457 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 17 are in fix.csv.

  • Route object: none2
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: none2402:7d80::/48Route objects for it name AS8075, AS63582, AS63583. A route object for 2402:7d80::/32 with origin AS138457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138457 in the RIR database for the space.9 of 636
Route object: none2402:7d80:8888::/48Route objects for it name AS8075, AS63582, AS63583. A route object for 2402:7d80::/32 with origin AS138457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138457 in the RIR database for the space.9 of 636

Route objects not announced

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

45.120.240.0/22APNICNo ROA
45.120.240.0/23APNICNo ROA
45.120.240.0/24APNICValid
45.120.241.0/24APNICValid
45.120.242.0/23APNICNo ROA
45.120.242.0/24APNICValid
103.61.60.0/22APNICNo ROA
103.61.60.0/23APNICNo ROA
103.61.62.0/23APNICNo ROA
103.126.16.0/24APNICNo ROA
103.126.17.0/24APNICNo ROA
103.126.18.0/24APNICNo ROA
103.126.19.0/24APNICNo ROA
2402:7d80::/32APNICNo ROA
2404:240::/32APNICNo 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.