bgpreport

Network · data from 2026-11-12

AS27539 WRT-AS

Registry name: WRT-AS - West River Telecommunications Cooperative, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS27539, 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.
64.68.0.0/22 Valid RIR databaseARIN 671 100% 68
64.68.4.0/22 Valid RIR databaseARIN 671 100% 68
64.68.8.0/23 Valid RIR databaseARIN 671 100% 68
64.68.10.0/24 Valid RIR databaseARIN 671 100% 68
64.68.11.0/24 Valid RIR databaseARIN 671 100% 68
64.68.12.0/22 Valid RIR databaseARIN 671 100% 68
69.26.0.0/22 Valid RIR databaseARIN 671 100% 68
69.26.4.0/24 Valid RIR databaseARIN 671 100% 68
69.26.5.0/24 Valid RIR databaseARIN 671 100% 68
69.26.6.0/23 Valid RIR databaseARIN 671 100% 68
69.26.8.0/21 Valid RIR databaseARIN 671 100% 68
69.26.16.0/24 Valid RIR databaseARIN 671 100% 68
69.26.17.0/24 Valid RIR databaseARIN 671 100% 68
69.26.18.0/23 Valid RIR databaseARIN 671 100% 68
69.26.20.0/23 Valid RIR databaseARIN 671 100% 68
69.26.22.0/23 Valid RIR databaseARIN 671 100% 68
69.26.24.0/24 Valid RIR databaseARIN 671 100% 68
69.26.25.0/24 Valid RIR databaseARIN 671 100% 68
69.26.26.0/23 Valid RIR databaseARIN 671 100% 68
69.26.28.0/23 Valid RIR databaseARIN 671 100% 68
69.26.30.0/23 Valid RIR databaseARIN 671 100% 68
113.30.240.0/20 Valid RIR databaseARIN 671 100% 68
2604:a900:4000::/35 Valid RIR databaseARIN 635 100% 69
2604:a900:6000::/35 Valid RIR databaseARIN 635 100% 69
2604:a900:a000::/35 Valid RIR databaseARIN 635 100% 69
2604:a900:e000::/35 Valid RIR databaseARIN 635 100% 69
2604:a900::/35 Valid RIR databaseARIN 634 100% 69
2604:a900:2000::/35 Valid RIR databaseARIN 634 100% 69
2604:a900:8000::/35 Valid RIR databaseARIN 634 100% 69
2604:a900:c000::/35 Valid RIR databaseARIN 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS27539: AS-27539:AS-53284. 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 (AS27539 isn't in the set, or no route object for AS27539 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 objectsAS27539 in itNot covered
AS-27539:AS-53284 ARIN 2132 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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