bgpreport

Network · data from 2026-11-12

AS32932 COVIUS-AS32932 - Covius Shared Services, LLC

Registry name: COVIUS-AS32932 - Covius Shared Services, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS32932, 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.
8.44.140.0/24 No ROA None 673 100% 67
205.168.182.0/24 No ROA Other IRR onlyALTDB 673 100% 67
8.41.58.0/24 No ROA RIR databaseALTDB, ARIN 673 100% 67
192.174.69.0/24 Valid RIR databaseALTDB, ARIN 673 100% 67
2620:cd:c000::/48 Valid RIR databaseALTDB, ARIN 634 100% 67

AS-SET

AS32932 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 5 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none8.44.140.0/24No ROA covers it. Add a ROA for AS32932, maxLength 24.673 of 673
Route object: none8.44.140.0/24No route object for it. Add a route object with origin AS32932 in the RIR database for the space.673 of 673
ROA: none205.168.182.0/24No ROA covers it. Add a ROA for AS32932, maxLength 24.673 of 673
Route object: RIR205.168.182.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none8.41.58.0/24No ROA covers it. Add a ROA for AS32932, maxLength 24.673 of 673

Route objects not announced

Every route object with origin AS32932 is announced.

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.