bgpreport

Network · data from 2026-11-12

AS54142 WHITE-CLOUD-COMMUNICATIONS - White Cloud Communications US, LLC

Registry name: WHITE-CLOUD-COMMUNICATIONS - White Cloud Communications US, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54142, 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.
104.232.6.0/23 No ROA Nonecovered by 104.232.4.0/22 673 100% 67
12.71.219.0/24 No ROA Other IRR onlyRADB 673 100% 67
104.232.4.0/24 No ROA Other IRR onlyRADB 673 100% 67
104.232.5.0/24 No ROA Other IRR onlyRADB 673 100% 67
199.180.104.0/21 No ROA Other IRR onlyRADB 673 100% 67
207.140.8.0/21 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS54142 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 30 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none104.232.6.0/23No ROA covers it. Add a ROA for AS54142, maxLength 23.673 of 673
Route object: none104.232.6.0/23No route object for it. A route object for 104.232.4.0/22 with origin AS54142 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54142 in the RIR database for the space.673 of 673
ROA: none12.71.219.0/24No ROA covers it. Add a ROA for AS54142, maxLength 24.673 of 673
Route object: RIR12.71.219.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none104.232.4.0/24No ROA covers it. Add a ROA for AS54142, maxLength 24.673 of 673
Route object: RIR104.232.4.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none104.232.5.0/24No ROA covers it. Add a ROA for AS54142, maxLength 24.673 of 673
Route object: RIR104.232.5.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.180.104.0/21No ROA covers it. Add a ROA for AS54142, maxLength 21.673 of 673
Route object: RIR199.180.104.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none207.140.8.0/21No ROA covers it. Add a ROA for AS54142, maxLength 21.673 of 673
Route object: RIR207.140.8.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

12.71.220.0/23RADBNo ROA
12.182.124.0/23ALTDB, RADBNo ROA
12.190.196.0/22RADBNo ROA
12.190.196.0/24RADBNo ROA
12.190.197.0/24RADBNo ROA
12.190.198.0/24RADBNo ROA
98.16.120.0/22RADBValid
104.232.4.0/22RADBNo ROA
199.30.72.0/21RADBNo ROA
199.30.72.0/24RADBNo ROA
199.30.73.0/24RADBNo ROA
199.30.75.0/24RADBNo ROA
199.180.104.0/22RADBNo ROA
199.180.108.0/23ALTDB, RADBNo ROA
199.180.110.0/23RADBNo ROA
199.180.110.0/24RADBNo ROA
199.180.111.0/24RADBNo ROA
2602:fcda::/36RADBNo 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.