bgpreport

Network · data from 2026-11-12

AS63322 PARLER-CLOUD

Registry name: PARLER-CLOUD - Parler Cloud, US · PeeringDB

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

Announced routes

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

142.147.3.0/24 No ROA Other origin onlycovered by 142.147.0.0/21 670 100% 68
142.147.4.0/24 No ROA Other origin onlycovered by 142.147.0.0/21 670 100% 68
142.147.5.0/24 No ROA Other origin onlycovered by 142.147.0.0/21 670 100% 68
142.147.6.0/24 No ROA Other origin onlycovered by 142.147.0.0/21 670 100% 68
142.147.7.0/24 No ROA Other origin onlycovered by 142.147.0.0/21 670 100% 68
142.147.0.0/23 No ROA Other IRR onlyNTTCOM 670 100% 68

AS-SET

AS63322's PeeringDB record names no 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 16 are in fix.csv.

  • ROA: none6
  • Route object: none5
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none142.147.3.0/24No ROA covers it. Add a ROA for AS63322, maxLength 24.670 of 673
Route object: none142.147.3.0/24Route objects for it name AS7819. A route object for 142.147.0.0/21 with origin AS63322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63322 in the RIR database for the space.670 of 673
ROA: none142.147.4.0/24No ROA covers it. Add a ROA for AS63322, maxLength 24.670 of 673
Route object: none142.147.4.0/24Route objects for it name AS7819. A route object for 142.147.0.0/21 with origin AS63322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63322 in the RIR database for the space.670 of 673
ROA: none142.147.5.0/24No ROA covers it. Add a ROA for AS63322, maxLength 24.670 of 673
Route object: none142.147.5.0/24Route objects for it name AS7819. A route object for 142.147.0.0/21 with origin AS63322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63322 in the RIR database for the space.670 of 673
ROA: none142.147.6.0/24No ROA covers it. Add a ROA for AS63322, maxLength 24.670 of 673
Route object: none142.147.6.0/24Route objects for it name AS7819. A route object for 142.147.0.0/21 with origin AS63322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63322 in the RIR database for the space.670 of 673
ROA: none142.147.7.0/24No ROA covers it. Add a ROA for AS63322, maxLength 24.670 of 673
Route object: none142.147.7.0/24Route objects for it name AS7819. A route object for 142.147.0.0/21 with origin AS63322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63322 in the RIR database for the space.670 of 673
ROA: none142.147.0.0/23No ROA covers it. Add a ROA for AS63322, maxLength 23.670 of 673
Route object: RIR142.147.0.0/23Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

23.150.192.0/24NTTCOMNo ROA
135.84.96.0/23NTTCOMNo ROA
142.147.0.0/21NTTCOMNo ROA
2001:470:312::/48ARINValid

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.