bgpreport

Network · data from 2026-11-12

AS54561 SECUREDRAGON - Secure Dragon LLC.

Registry name: SECUREDRAGON - Secure Dragon LLC., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54561, 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.

198.57.47.0/24 No ROA Other IRR onlyRADB 666 99% 68
2602:fff6:7::/48 No ROA Other IRR onlyRADB 633 100% 69

AS-SET

AS54561 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 10 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none198.57.47.0/24No ROA covers it. Add a ROA for AS54561, maxLength 24.666 of 673
Route object: RIR198.57.47.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none2602:fff6:7::/48No ROA covers it. Add a ROA for AS54561, maxLength 48.633 of 636
Route object: RIR2602:fff6:7::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

198.57.44.0/24RADBNo ROA
198.57.45.0/24RADBNo ROA
199.167.28.0/22RADBNo ROA
199.167.29.0/24RADBNo ROA
199.167.30.0/24RADBNo ROA
199.167.31.0/24RADBNo 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.