bgpreport

Network · data from 2026-11-12

AS55641 Oneworld-Group - Changping District, Beijing

Registry name: Oneworld-Group - Changping District, Beijing, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55641, 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.
2401:be00::/32 No ROA None 386 61% 65
2401:be00:5::/48 No ROA None 383 60% 65
2401:be00::/48 Valid Other origin only 287 45% 65

AS-SET

AS55641 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 12 are in fix.csv.

  • ROA: none2
  • Route object: none3
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2401:be00::/32No ROA covers it. Add a ROA for AS55641, maxLength 32.386 of 636
Route object: none2401:be00::/32No route object for it. Add a route object with origin AS55641 in the RIR database for the space.386 of 636
ROA: none2401:be00:5::/48No ROA covers it. Add a ROA for AS55641, maxLength 48.383 of 636
Route object: none2401:be00:5::/48No route object for it. Add a route object with origin AS55641 in the RIR database for the space.383 of 636
Route object: none2401:be00::/48Route objects for it name AS23724. Add a route object with origin AS55641 in the RIR database for the space.287 of 636

Route objects not announced

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

122.10.216.0/22NTTCOM, RADBNo ROA
122.10.216.0/23NTTCOM, RADBNo ROA
122.10.216.0/24NTTCOM, RADBNo ROA
122.10.217.0/24NTTCOM, RADBNo ROA
122.10.218.0/23NTTCOM, RADBNo ROA
122.10.218.0/24NTTCOM, RADBNo ROA
122.10.219.0/24NTTCOM, 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.