bgpreport

Network · data from 2026-11-12

AS136725 CHENJITONG-AS-AP - Chen Jitong

Registry name: CHENJITONG-AS-AP - Chen Jitong, CN · not in PeeringDB

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

Announced routes

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

16.217.6.0/24 Invalid: origin None 2 0%low visibility 2
45.139.182.0/24 Invalid: origin Other origin only 2 0%low visibility 2
162.141.140.0/24 Invalid: origin Other origin only 2 0%low visibility 2
178.83.133.0/24 Invalid: origin Other origin only 2 0%low visibility 2
185.191.20.0/24 Invalid: origin None 2 0%low visibility 2
79.176.213.0/24 Invalid: origin None 1 0%low visibility 1
79.176.227.0/24 Invalid: origin None 1 0%low visibility 1
109.66.24.0/24 Invalid: origin Other origin only 1 0%low visibility 1
155.117.138.0/24 Invalid: origin None 1 0%low visibility 1
178.95.192.0/24 Invalid: origin None 1 0%low visibility 1
213.189.17.0/24 Invalid: origin None 1 0%low visibility 1
213.218.216.0/24 Invalid: origin Other origin only 1 0%low visibility 1
154.94.60.0/24 Invalid: origin RIR databaseAFRINIC 1 0%low visibility 1
107.149.9.0/24 No ROA Other origin only 2 0%low visibility 2
2406:840:fc10::/48 Valid RIR databaseAPNIC 636 100% 68
2406:840:fc11::/48 Valid RIR databaseAPNIC 636 100% 68
2406:840:fc12::/48 Valid RIR databaseAPNIC 636 100% 68
2406:840:fc13::/48 Valid RIR databaseAPNIC 635 100% 67
2406:840:fea4::/48 Valid RIR databaseAPNIC 634 100% 69

AS-SET

AS136725 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 58 are in fix.csv.

  • ROA: origin13
  • ROA: none1
  • Route object: none13
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
ROA: origin16.217.6.0/24ROAs covering it name AS5650, not AS136725. If AS136725 should announce it, add a ROA for AS136725.2 of 673
Route object: none16.217.6.0/24No route object for it. Add a route object with origin AS136725 in the RIR database for the space.2 of 673
ROA: origin45.139.182.0/24ROAs covering it name AS138887, not AS136725. If AS136725 should announce it, add a ROA for AS136725.2 of 673
Route object: none45.139.182.0/24Route objects for it name AS138887. Add a route object with origin AS136725 in the RIR database for the space.2 of 673
ROA: origin162.141.140.0/24ROAs covering it name AS834, not AS136725. If AS136725 should announce it, add a ROA for AS136725.2 of 673
Route object: none162.141.140.0/24Route objects for it name AS834. Add a route object with origin AS136725 in the RIR database for the space.2 of 673
ROA: origin178.83.133.0/24ROAs covering it name AS214647, not AS136725. If AS136725 should announce it, add a ROA for AS136725.2 of 673
Route object: none178.83.133.0/24Route objects for it name AS214647. Add a route object with origin AS136725 in the RIR database for the space.2 of 673
ROA: origin185.191.20.0/24ROAs covering it name AS834, not AS136725. If AS136725 should announce it, add a ROA for AS136725.2 of 673
Route object: none185.191.20.0/24No route object for it. Add a route object with origin AS136725 in the RIR database for the space.2 of 673
ROA: origin79.176.213.0/24ROAs covering it name AS834, not AS136725. If AS136725 should announce it, add a ROA for AS136725.1 of 673
Route object: none79.176.213.0/24No route object for it. Add a route object with origin AS136725 in the RIR database for the space.1 of 673
ROA: origin79.176.227.0/24ROAs covering it name AS834, not AS136725. If AS136725 should announce it, add a ROA for AS136725.1 of 673
Route object: none79.176.227.0/24No route object for it. Add a route object with origin AS136725 in the RIR database for the space.1 of 673
ROA: origin109.66.24.0/24ROAs covering it name AS206092, not AS136725. If AS136725 should announce it, add a ROA for AS136725.1 of 673
Route object: none109.66.24.0/24Route objects for it name AS206092. Add a route object with origin AS136725 in the RIR database for the space.1 of 673
ROA: origin155.117.138.0/24ROAs covering it name AS834, not AS136725. If AS136725 should announce it, add a ROA for AS136725.1 of 673
Route object: none155.117.138.0/24No route object for it. Add a route object with origin AS136725 in the RIR database for the space.1 of 673
ROA: origin178.95.192.0/24ROAs covering it name AS834, AS20473, not AS136725. If AS136725 should announce it, add a ROA for AS136725.1 of 673
Route object: none178.95.192.0/24No route object for it. Add a route object with origin AS136725 in the RIR database for the space.1 of 673
ROA: origin213.189.17.0/24ROAs covering it name AS834, AS8315, not AS136725. If AS136725 should announce it, add a ROA for AS136725.1 of 673
Route object: none213.189.17.0/24No route object for it. Add a route object with origin AS136725 in the RIR database for the space.1 of 673
ROA: origin213.218.216.0/24ROAs covering it name AS834, AS8851, AS19905, not AS136725. If AS136725 should announce it, add a ROA for AS136725.1 of 673
Route object: none213.218.216.0/24Route objects for it name AS834. Add a route object with origin AS136725 in the RIR database for the space.1 of 673
ROA: origin154.94.60.0/24ROAs covering it name AS17561, AS137410, AS218661, not AS136725. If AS136725 should announce it, add a ROA for AS136725.1 of 673
ROA: none107.149.9.0/24No ROA covers it. Add a ROA for AS136725, maxLength 24.2 of 673
Route object: none107.149.9.0/24Route objects for it name AS834. Add a route object with origin AS136725 in the RIR database for the space.2 of 673

Route objects not announced

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

45.196.104.0/24AFRINICInvalid: origin
45.196.165.0/24AFRINICInvalid: origin
154.198.10.0/24AFRINICInvalid: origin
154.208.67.0/24AFRINICInvalid: origin
2406:840:fc10::/44APNICValid
2406:840:fc10::/45APNICValid
2406:840:fc10::/46APNICValid
2406:840:fc10::/47APNICValid
2406:840:fc12::/47APNICValid
2406:840:fc14::/46APNICValid
2406:840:fc14::/47APNICValid
2406:840:fc14::/48APNICValid
2406:840:fc15::/48APNICValid
2406:840:fc16::/47APNICValid
2406:840:fc16::/48APNICValid
2406:840:fc17::/48APNICValid
2406:840:fc18::/45APNICValid
2406:840:fc18::/46APNICValid
2406:840:fc18::/47APNICValid
2406:840:fc18::/48APNICValid
2406:840:fc19::/48APNICValid
2406:840:fc1a::/47APNICValid
2406:840:fc1a::/48APNICValid
2406:840:fc1b::/48APNICValid
2406:840:fc1c::/46APNICValid
2406:840:fc1c::/47APNICValid
2406:840:fc1c::/48APNICValid
2406:840:fc1d::/48APNICValid
2406:840:fc1e::/47APNICValid
2406:840:fc1e::/48APNICValid
2406:840:fc1f::/48APNICValid

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.