Network · data from 2026-11-12
AS207343 BOJING BOJING CO., LIMITED
Registry name: BOJING BOJING CO., LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207343, 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.
| 89.213.205.0/24 | Invalid: origin | None | 2 0%low visibility |
| 185.227.255.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 151.246.104.0/24 | Valid | RIR databaseRADB, RIPE | 1 0%low visibility |
AS-SET
AS207343 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 8 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 89.213.205.0/24 | ROAs covering it name AS834, AS8851, AS19905, not AS207343. If AS207343 should announce it, add a ROA for AS207343. |
| Route object: none | 89.213.205.0/24 | No route object for it. Add a route object with origin AS207343 in the RIR database for the space. |
| ROA: origin | 185.227.255.0/24 | ROAs covering it name AS152606, not AS207343. If AS207343 should announce it, add a ROA for AS207343. |
| Route object: none | 185.227.255.0/24 | Route objects for it name AS152606. Add a route object with origin AS207343 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS207343 whose prefix no peer sees AS207343 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 143.20.1.0/24 | RADB, RIPE | Valid |
| 143.20.17.0/24 | RADB, RIPE | Valid |
| 151.242.96.0/24 | RIPE | Invalid: origin |
| 2602:feda:c20::/44 | ARIN | No 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.