bgpreport

Network · data from 2026-11-12

AS139811 ANLIANNETWORK-AS-AP - ANLIAN NETWORK TECHNOLOGY CO., LIMITED

Registry name: ANLIANNETWORK-AS-AP - ANLIAN NETWORK TECHNOLOGY CO., LIMITED, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS139811, 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.
154.210.13.0/24 Invalid: origin Other origin only 25 4%low visibility 15
154.205.4.0/24 Valid Other IRR onlyNTTCOM 672 100% 67
156.240.93.0/24 Valid Other IRR onlyRADB 671 100% 67
156.249.24.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
156.249.25.0/24 Valid Other IRR onlyRADB 671 100% 67
154.205.5.0/24 Valid Other IRR onlyNTTCOM 670 100% 66
103.145.145.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.145.144.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
154.91.39.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
154.210.12.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
154.210.15.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 66
45.195.61.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 669 99% 66

AS-SET

AS139811 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 10 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin154.210.13.0/24ROAs covering it name AS17561, AS401362, not AS139811. If AS139811 should announce it, add a ROA for AS139811.25 of 673
Route object: none154.210.13.0/24Route objects for it name AS401362. Add a route object with origin AS139811 in the RIR database for the space.25 of 673
Route object: RIR154.205.4.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR156.240.93.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR156.249.24.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR156.249.25.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR154.205.5.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

103.145.144.0/23APNICValid
154.205.4.0/23AFRINIC, RADBValid
156.249.24.0/23AFRINIC, RADBValid

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.