bgpreport

Network · data from 2026-11-12

AS54281 Wild Turkey Acres

Registry name: WTA-WV - Wild Turkey Acres WV LLC, US · PeeringDB

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

Announced routes

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

2602:f8c6:54::/48 No ROA Nonecovered by 2602:f8c6::/40 636 100% 68
23.180.200.0/24 No ROA RIR databaseARIN 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS54281: AS396186:AS-FRIENDS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS54281 isn't in the set, or no route object for AS54281 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS54281 in itNot covered
AS396186:AS-FRIENDS ARIN 4124 Yes 0

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: none2
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2602:f8c6:54::/48No ROA covers it. Add a ROA for AS54281, maxLength 48.636 of 636
Route object: none2602:f8c6:54::/48No route object for it. A route object for 2602:f8c6::/40 with origin AS54281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54281 in the RIR database for the space.636 of 636
ROA: none23.180.200.0/24No ROA covers it. Add a ROA for AS54281, maxLength 24.673 of 673

Route objects not announced

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

44.30.21.0/24RADBNo ROA
131.143.79.0/24ARINNo ROA
2602:f8c6::/40ARIN, RADBNo ROA
2602:f8c6:55::/48ARINNo ROA
2602:f8c6:79::/48ARINNo 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.