bgpreport

Network · data from 2026-11-12

AS63621 NXBCTV-NET - NINGXIA BROADCAST&TV NETWORK CO.,LTD

Registry name: NXBCTV-NET - NINGXIA BROADCAST&TV NETWORK CO.,LTD, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63621, 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.
117.124.237.0/24 Invalid: origin None 9 1%low visibility 5
240a:4010:8000::/33 Valid None 69 11% 34
240a:4084:2000::/35 Valid None 69 11% 34
240a:408c:2000::/35 Valid None 69 11% 34
240a:4094:2000::/35 Valid None 69 11% 34
240a:409c:2000::/35 Valid None 69 11% 34
240a:40a4:2000::/35 Valid None 69 11% 34
240a:40ac:2000::/35 Valid None 69 11% 34
240a:4172::/31 Valid None 69 11% 34
240a:41f2::/31 Valid None 69 11% 34
240a:4242::/31 Valid None 69 11% 34
163.61.202.0/23 Valid None 57 8%low visibility 33
45.253.60.0/22 Valid Other IRR onlyNTTCOM, RADB 57 8%low visibility 33
103.222.184.0/22 Valid Other IRR onlyNTTCOM, RADB 57 8%low visibility 33

AS-SET

AS63621 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 16 are in fix.csv.

  • ROA: origin1
  • Route object: none12
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin117.124.237.0/24ROAs covering it name AS146788, not AS63621. If AS63621 should announce it, add a ROA for AS63621.9 of 673
Route object: none117.124.237.0/24No route object for it. Add a route object with origin AS63621 in the RIR database for the space.9 of 673
Route object: none240a:4010:8000::/33No route object for it. Add a route object with origin AS63621 in the RIR database for the space.69 of 636
Route object: none240a:4084:2000::/35No route object for it. Add a route object with origin AS63621 in the RIR database for the space.69 of 636
Route object: none240a:408c:2000::/35No route object for it. Add a route object with origin AS63621 in the RIR database for the space.69 of 636
Route object: none240a:4094:2000::/35No route object for it. Add a route object with origin AS63621 in the RIR database for the space.69 of 636
Route object: none240a:409c:2000::/35No route object for it. Add a route object with origin AS63621 in the RIR database for the space.69 of 636
Route object: none240a:40a4:2000::/35No route object for it. Add a route object with origin AS63621 in the RIR database for the space.69 of 636
Route object: none240a:40ac:2000::/35No route object for it. Add a route object with origin AS63621 in the RIR database for the space.69 of 636
Route object: none240a:4172::/31No route object for it. Add a route object with origin AS63621 in the RIR database for the space.69 of 636
Route object: none240a:41f2::/31No route object for it. Add a route object with origin AS63621 in the RIR database for the space.69 of 636
Route object: none240a:4242::/31No route object for it. Add a route object with origin AS63621 in the RIR database for the space.69 of 636
Route object: none163.61.202.0/23No route object for it. Add a route object with origin AS63621 in the RIR database for the space.57 of 673
Route object: RIR45.253.60.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.57 of 673
Route object: RIR103.222.184.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.57 of 673

Route objects not announced

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

2407:7980::/32NTTCOM, RADBNo 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.