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
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% |
| 117.74.68.0/22 | Valid | None | 672 100% |
| 103.79.200.0/22 | Valid | Other origin only | 109 16% |
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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 103.79.203.0/24 | ROA 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. |
| Route object: none | 103.79.203.0/24 | No route object for it. Add a route object with origin AS45097 in the RIR database for the space. |
| Route object: none | 117.74.68.0/22 | No route object for it. Add a route object with origin AS45097 in the RIR database for the space. |
| Route object: none | 103.79.200.0/22 | Route objects for it name AS4847. Add a route object with origin AS45097 in the RIR database for the space. |
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.