bgpreport

Network · data from 2026-11-12

AS206278 NETCLOUDSTORAGE Net Cloud Storage LLC

Registry name: NETCLOUDSTORAGE Net Cloud Storage LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206278, 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.
185.222.196.0/23 No ROA Nonecovered by 185.222.196.0/22 673 100% 67
185.222.198.0/23 No ROA Nonecovered by 185.222.196.0/22 673 100% 67
45.93.24.0/22 No ROA RIR databaseRIPE 673 100% 67
185.191.4.0/22 No ROA RIR databaseRIPE 673 100% 67
185.234.124.0/22 No ROA RIR databaseRIPE 673 100% 67
185.243.100.0/23 No ROA RIR databaseRIPE 673 100% 67
185.243.102.0/23 No ROA RIR databaseRIPE 673 100% 67
194.50.236.0/22 No ROA RIR databaseRIPE 673 100% 67

AS-SET

AS206278 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: none8
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none185.222.196.0/23No ROA covers it. Add a ROA for AS206278, maxLength 23.673 of 673
Route object: none185.222.196.0/23No route object for it. A route object for 185.222.196.0/22 with origin AS206278 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206278 in the RIR database for the space.673 of 673
ROA: none185.222.198.0/23No ROA covers it. Add a ROA for AS206278, maxLength 23.673 of 673
Route object: none185.222.198.0/23No route object for it. A route object for 185.222.196.0/22 with origin AS206278 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206278 in the RIR database for the space.673 of 673
ROA: none45.93.24.0/22No ROA covers it. Add a ROA for AS206278, maxLength 22.673 of 673
ROA: none185.191.4.0/22No ROA covers it. Add a ROA for AS206278, maxLength 22.673 of 673
ROA: none185.234.124.0/22No ROA covers it. Add a ROA for AS206278, maxLength 22.673 of 673
ROA: none185.243.100.0/23No ROA covers it. Add a ROA for AS206278, maxLength 23.673 of 673
ROA: none185.243.102.0/23No ROA covers it. Add a ROA for AS206278, maxLength 23.673 of 673
ROA: none194.50.236.0/22No ROA covers it. Add a ROA for AS206278, maxLength 22.673 of 673

Route objects not announced

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

185.222.196.0/22RIPENo ROA
2a0a:1340::/29RIPENo 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.