bgpreport

Network · data from 2026-11-12

AS36201 B2X-ONLINE-WISP-ASN - B2X Online Inc

Registry name: B2X-ONLINE-WISP-ASN - B2X Online Inc, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36201, 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.
162.213.85.0/24 No ROA Nonecovered by 162.213.84.0/22 673 100% 67
162.213.86.0/24 No ROA Nonecovered by 162.213.84.0/22 673 100% 67
162.213.87.0/24 No ROA Nonecovered by 162.213.84.0/22 673 100% 67
208.69.224.0/24 No ROA Nonecovered by 208.69.224.0/22 673 100% 67
208.69.225.0/24 No ROA Nonecovered by 208.69.224.0/22 673 100% 67
208.69.227.0/24 No ROA Nonecovered by 208.69.224.0/22 673 100% 67
162.213.84.0/24 No ROA Nonecovered by 162.213.84.0/22 672 100% 67
208.69.226.0/24 No ROA Nonecovered by 208.69.224.0/22 672 100% 67
192.111.251.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
192.188.84.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67

AS-SET

AS36201 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 23 are in fix.csv.

  • ROA: none10
  • Route object: none8
  • Route object: RIR2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none162.213.85.0/24No ROA covers it. Add a ROA for AS36201, maxLength 24.673 of 673
Route object: none162.213.85.0/24No route object for it. A route object for 162.213.84.0/22 with origin AS36201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36201 in the RIR database for the space.673 of 673
ROA: none162.213.86.0/24No ROA covers it. Add a ROA for AS36201, maxLength 24.673 of 673
Route object: none162.213.86.0/24No route object for it. A route object for 162.213.84.0/22 with origin AS36201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36201 in the RIR database for the space.673 of 673
ROA: none162.213.87.0/24No ROA covers it. Add a ROA for AS36201, maxLength 24.673 of 673
Route object: none162.213.87.0/24No route object for it. A route object for 162.213.84.0/22 with origin AS36201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36201 in the RIR database for the space.673 of 673
ROA: none208.69.224.0/24No ROA covers it. Add a ROA for AS36201, maxLength 24.673 of 673
Route object: none208.69.224.0/24No route object for it. A route object for 208.69.224.0/22 with origin AS36201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36201 in the RIR database for the space.673 of 673
ROA: none208.69.225.0/24No ROA covers it. Add a ROA for AS36201, maxLength 24.673 of 673
Route object: none208.69.225.0/24No route object for it. A route object for 208.69.224.0/22 with origin AS36201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36201 in the RIR database for the space.673 of 673
ROA: none208.69.227.0/24No ROA covers it. Add a ROA for AS36201, maxLength 24.673 of 673
Route object: none208.69.227.0/24No route object for it. A route object for 208.69.224.0/22 with origin AS36201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36201 in the RIR database for the space.673 of 673
ROA: none162.213.84.0/24No ROA covers it. Add a ROA for AS36201, maxLength 24.672 of 673
Route object: none162.213.84.0/24No route object for it. A route object for 162.213.84.0/22 with origin AS36201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36201 in the RIR database for the space.672 of 673
ROA: none208.69.226.0/24No ROA covers it. Add a ROA for AS36201, maxLength 24.672 of 673
Route object: none208.69.226.0/24No route object for it. A route object for 208.69.224.0/22 with origin AS36201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36201 in the RIR database for the space.672 of 673
ROA: none192.111.251.0/24No ROA covers it. Add a ROA for AS36201, maxLength 24.673 of 673
Route object: RIR192.111.251.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.188.84.0/24No ROA covers it. Add a ROA for AS36201, maxLength 24.673 of 673
Route object: RIR192.188.84.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

162.213.84.0/22NTTCOM, RADBNo ROA
208.69.224.0/22NTTCOM, RADBNo ROA
209.170.176.0/20RADBNo 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.