bgpreport

Network · data from 2026-11-12

AS399033 DUCOR-01 - VARCOMM BROADBAND, INC.

Registry name: DUCOR-01 - VARCOMM BROADBAND, INC., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS399033, 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.
50.115.199.0/24 Invalid: origin None 28 4%low visibility 23
98.158.16.0/24 Invalid: maxLength Nonecovered by 98.158.16.0/22 28 4%low visibility 23
199.190.162.0/24 No ROA Other origin only 673 100% 67
66.62.180.0/23 Valid None 673 100% 67
2001:438:4a::/48 Valid None 635 100% 68
98.158.16.0/22 Valid RIR databaseARIN, RADB 671 100% 69

AS-SET

AS399033 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 8 are in fix.csv.

  • ROA: origin1
  • ROA: maxLength1
  • ROA: none1
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: origin50.115.199.0/24ROAs covering it name AS54048, not AS399033. If AS399033 should announce it, add a ROA for AS399033.28 of 673
Route object: none50.115.199.0/24No route object for it. Add a route object with origin AS399033 in the RIR database for the space.28 of 673
ROA: maxLength98.158.16.0/24ROA 98.158.16.0/22 AS399033 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 98.158.16.0/24.28 of 673
Route object: none98.158.16.0/24No route object for it. A route object for 98.158.16.0/22 with origin AS399033 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399033 in the RIR database for the space.28 of 673
ROA: none199.190.162.0/24No ROA covers it. Add a ROA for AS399033, maxLength 24.673 of 673
Route object: none199.190.162.0/24Route objects for it name AS54667. Add a route object with origin AS399033 in the RIR database for the space.673 of 673
Route object: none66.62.180.0/23No route object for it. Add a route object with origin AS399033 in the RIR database for the space.673 of 673
Route object: none2001:438:4a::/48No route object for it. Add a route object with origin AS399033 in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS399033 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.