bgpreport

Network · data from 2026-11-12

AS131565 IMBTVN - INNER MONGOLIA BROADCAST&TV NETWORK GROUP CORPORATION

Registry name: IMBTVN - INNER MONGOLIA BROADCAST&TV NETWORK GROUP CORPORATION, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS131565, 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.
45.119.119.0/24 Invalid: maxLength None 9 1%low visibility 5
45.115.200.0/22 Valid Other origin only 105 16% 41
45.116.152.0/22 Valid None 105 16% 41
103.55.228.0/22 Valid Other origin only 105 16% 41
103.230.200.0/22 Valid None 105 16% 41
43.254.168.0/22 Valid None 57 8%low visibility 33
45.119.116.0/22 Valid None 57 8%low visibility 33
202.164.0.0/20 Valid None 57 8%low visibility 33

AS-SET

AS131565 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 9 are in fix.csv.

  • ROA: maxLength1
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: maxLength45.119.119.0/24ROA 45.119.116.0/22 AS131565 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 45.119.119.0/24.9 of 673
Route object: none45.119.119.0/24No route object for it. Add a route object with origin AS131565 in the RIR database for the space.9 of 673
Route object: none45.115.200.0/22Route objects for it name AS4837. Add a route object with origin AS131565 in the RIR database for the space.105 of 673
Route object: none45.116.152.0/22No route object for it. Add a route object with origin AS131565 in the RIR database for the space.105 of 673
Route object: none103.55.228.0/22Route objects for it name AS4808. Add a route object with origin AS131565 in the RIR database for the space.105 of 673
Route object: none103.230.200.0/22No route object for it. Add a route object with origin AS131565 in the RIR database for the space.105 of 673
Route object: none43.254.168.0/22No route object for it. Add a route object with origin AS131565 in the RIR database for the space.57 of 673
Route object: none45.119.116.0/22No route object for it. Add a route object with origin AS131565 in the RIR database for the space.57 of 673
Route object: none202.164.0.0/20No route object for it. Add a route object with origin AS131565 in the RIR database for the space.57 of 673

Route objects not announced

Every route object with origin AS131565 is announced.

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.