bgpreport

Network · data from 2026-11-12

AS20446 DUKELANA-20446 - Dukelana

Registry name: DUKELANA-20446 - Dukelana, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20446, 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.
44.30.66.0/24 No ROA Other IRR onlyRADB 670 100% 68
2602:f4ca:e3::/48 Valid Nonecovered by 2602:f4ca:e0::/44 632 99% 69
2602:f4ca:e4::/48 Valid Nonecovered by 2602:f4ca:e0::/44 632 99% 69
2602:f4ca:e5::/48 Valid Nonecovered by 2602:f4ca:e0::/44 632 99% 69
204.154.108.0/24 Valid RIR databaseARIN 670 100% 68
2602:f4ca::/48 Valid RIR databaseARIN 632 99% 69
2602:f4ca:1d::/48 Valid RIR databaseARIN 632 99% 69

AS-SET

AS20446 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: none1
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none44.30.66.0/24No ROA covers it. Add a ROA for AS20446, maxLength 24.670 of 673
Route object: RIR44.30.66.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: none2602:f4ca:e3::/48No route object for it. A route object for 2602:f4ca:e0::/44 with origin AS20446 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20446 in the RIR database for the space.632 of 636
Route object: none2602:f4ca:e4::/48No route object for it. A route object for 2602:f4ca:e0::/44 with origin AS20446 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20446 in the RIR database for the space.632 of 636
Route object: none2602:f4ca:e5::/48No route object for it. A route object for 2602:f4ca:e0::/44 with origin AS20446 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20446 in the RIR database for the space.632 of 636

Route objects not announced

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

2001:4de0:ac10::/48ALTDBInvalid: origin
2001:4de0:ac18::/48ALTDBInvalid: origin
2001:4de0:ac19::/48ALTDBInvalid: origin
2602:f4ca:1::/48ARINValid
2602:f4ca:8::/48ARINValid
2602:f4ca:e0::/44ARINValid
2602:f831:e0::/44ARINValid

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.