bgpreport

Network · data from 2026-11-12

AS45097 baolirongtong - Poly facility (Beijing) Technology Co., Ltd.

Registry name: baolirongtong - Poly facility (Beijing) Technology Co., Ltd., CN · not in PeeringDB

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

Announced routes

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

103.79.203.0/24 Invalid: maxLength None 132 20% 54
117.74.68.0/22 Valid None 672 100% 67
103.79.200.0/22 Valid Other origin only 109 16% 44

AS-SET

AS45097 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 4 are in fix.csv.

  • ROA: maxLength1
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.79.203.0/24ROA 103.79.200.0/22 AS45097 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 103.79.203.0/24.132 of 673
Route object: none103.79.203.0/24No route object for it. Add a route object with origin AS45097 in the RIR database for the space.132 of 673
Route object: none117.74.68.0/22No route object for it. Add a route object with origin AS45097 in the RIR database for the space.672 of 673
Route object: none103.79.200.0/22Route objects for it name AS4847. Add a route object with origin AS45097 in the RIR database for the space.109 of 673

Route objects not announced

Every route object with origin AS45097 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.