bgpreport

Network · data from 2026-11-12

AS133111 CNT-northChina - CERNET New Technology Co., Ltd

Registry name: CNT-northChina - CERNET New Technology Co., Ltd, CN · not in PeeringDB

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

Announced routes

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

42.245.221.0/24 No ROA Nonecovered by 42.245.192.0/18 672 100% 67
42.245.192.0/18 No ROA RIR databaseAPNIC 105 16% 44
2403:a200:9999::/48 Valid None 387 61% 65
103.81.200.0/22 Valid None 78 12% 40
42.201.33.0/24 Valid RIR databaseAPNIC 673 100% 67
42.201.60.0/23 Valid RIR databaseAPNIC 673 100% 67
2400:a980::/29 Valid RIR databaseAPNIC 634 100% 69
240d:4000::/21 Valid RIR databaseAPNIC 633 100% 69
42.201.32.0/19 Valid RIR databaseAPNIC 105 16% 44
42.201.62.0/23 Valid RIR databaseAPNIC 105 16% 44
43.252.48.0/24 Valid RIR databaseAPNIC 105 16% 44

AS-SET

AS133111 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 86 are in fix.csv.

  • ROA: none2
  • Route object: none3
  • Route object: not announced81
ChangePrefix or setDetailFull-table peers
ROA: none42.245.221.0/24No ROA covers it. Add a ROA for AS133111, maxLength 24.672 of 673
Route object: none42.245.221.0/24No route object for it. A route object for 42.245.192.0/18 with origin AS133111 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133111 in the RIR database for the space.672 of 673
ROA: none42.245.192.0/18No ROA covers it. Add a ROA for AS133111, maxLength 18.105 of 673
Route object: none2403:a200:9999::/48No route object for it. Add a route object with origin AS133111 in the RIR database for the space.387 of 636
Route object: none103.81.200.0/22No route object for it. Add a route object with origin AS133111 in the RIR database for the space.78 of 673

Route objects not announced

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

42.201.32.0/20APNICValid
42.201.32.0/21APNICValid
42.201.32.0/22APNICValid
42.201.32.0/23APNICValid
42.201.32.0/24APNICValid
42.201.34.0/23APNICValid
42.201.34.0/24APNICValid
42.201.35.0/24APNICValid
42.201.36.0/22APNICValid
42.201.36.0/23APNICValid
42.201.36.0/24APNICValid
42.201.37.0/24APNICValid
42.201.38.0/23APNICValid
42.201.38.0/24APNICValid
42.201.39.0/24APNICValid
42.201.40.0/21APNICValid
42.201.40.0/22APNICValid
42.201.40.0/23APNICValid
42.201.40.0/24APNICValid
42.201.41.0/24APNICValid
42.201.42.0/23APNICValid
42.201.42.0/24APNICValid
42.201.43.0/24APNICValid
42.201.44.0/22APNICValid
42.201.44.0/23APNICValid
42.201.44.0/24APNICValid
42.201.45.0/24APNICValid
42.201.46.0/23APNICValid
42.201.46.0/24APNICValid
42.201.47.0/24APNICValid
42.201.48.0/20APNICValid
42.201.48.0/21APNICValid
42.201.48.0/22APNICValid
42.201.48.0/23APNICValid
42.201.48.0/24APNICValid
42.201.49.0/24APNICValid
42.201.50.0/23APNICValid
42.201.50.0/24APNICValid
42.201.51.0/24APNICValid
42.201.52.0/22APNICValid
42.201.52.0/23APNICValid
42.201.52.0/24APNICValid
42.201.53.0/24APNICValid
42.201.54.0/23APNICValid
42.201.54.0/24APNICValid
42.201.55.0/24APNICValid
42.201.56.0/21APNICValid
42.201.56.0/22APNICValid
42.201.56.0/23APNICValid
42.201.56.0/24APNICValid
42.201.57.0/24APNICValid
42.201.58.0/23APNICValid
42.201.58.0/24APNICValid
42.201.59.0/24APNICValid
42.201.60.0/22APNICValid
42.201.60.0/24APNICValid
42.201.61.0/24APNICValid
42.201.62.0/24APNICValid
42.201.63.0/24APNICValid
2400:a980::/40APNICInvalid: maxLength
2400:a980:bf::/48APNICInvalid: maxLength
2400:a980:d1::/48APNICInvalid: maxLength
2400:a980:da::/48APNICInvalid: maxLength
2400:a980:e1::/48APNICInvalid: maxLength
2400:a980:e3::/48APNICInvalid: maxLength
2400:a980:ef::/48APNICInvalid: maxLength
2400:a980:1800::/40APNICInvalid: maxLength
2400:a980:18fe::/48APNICInvalid: maxLength
2400:a980:18ff::/48APNICInvalid: maxLength
2400:a980:2000::/40APNICInvalid: maxLength
2400:a980:2800::/40APNICInvalid: maxLength
2400:a980:2c00::/40APNICInvalid: maxLength
2400:a980:5800::/40APNICInvalid: maxLength
2400:a980:6400::/40APNICInvalid: maxLength
2400:a980:6800::/40APNICInvalid: maxLength
2400:a980:7400::/40APNICInvalid: maxLength
2400:a980:7800::/40APNICInvalid: maxLength
2400:a980:9000::/40APNICInvalid: maxLength
2400:a980:90fd::/48APNICInvalid: maxLength
2400:a980:90ff::/48APNICInvalid: maxLength
2400:a980:a000::/40APNICValid

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.