bgpreport

Network · data from 2026-11-12

AS15191 Western Independent Networks

Registry name: WIN-NET - Western Independent Networks, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS15191, 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.140.28.0/22 No ROA Other IRR onlyALTDB 671 100% 68
198.29.32.0/22 Valid Nonecovered by 198.29.32.0/20 671 100% 68
198.29.40.0/22 Valid Nonecovered by 198.29.32.0/20 671 100% 68
198.29.45.0/24 Valid Nonecovered by 198.29.44.0/22 671 100% 68
198.135.156.0/23 Valid Nonecovered by 198.135.156.0/22 671 100% 68
198.29.36.0/22 Valid RIR databaseARIN 671 100% 68
198.29.40.0/23 Valid RIR databaseARIN 671 100% 68
198.29.44.0/22 Valid RIR databaseARIN 671 100% 68
198.135.156.0/22 Valid RIR databaseARIN 671 100% 68
2604:4180::/32 Valid RIR databaseARIN 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS15191: ARIN::AS-WIN-15191. 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 (AS15191 isn't in the set, or no route object for AS15191 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 objectsAS15191 in itNot covered
ARIN::AS-WIN-15191 ARIN 9178 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 13 are in fix.csv.

  • ROA: none1
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none198.140.28.0/22No ROA covers it. Add a ROA for AS15191, maxLength 22.671 of 673
Route object: RIR198.140.28.0/22Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: none198.29.32.0/22No route object for it. A route object for 198.29.32.0/20 with origin AS15191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15191 in the RIR database for the space.671 of 673
Route object: none198.29.40.0/22No route object for it. A route object for 198.29.32.0/20 with origin AS15191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15191 in the RIR database for the space.671 of 673
Route object: none198.29.45.0/24No route object for it. A route object for 198.29.44.0/22 with origin AS15191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15191 in the RIR database for the space.671 of 673
Route object: none198.135.156.0/23No route object for it. A route object for 198.135.156.0/22 with origin AS15191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15191 in the RIR database for the space.671 of 673

Route objects not announced

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

38.134.234.0/24RADBNo ROA
140.82.242.0/23RADBNo ROA
140.82.246.0/24RADBNo ROA
165.140.88.0/22RADBNo ROA
198.29.32.0/20ARIN, RADBValid
2001:470:64a::/47ARINValid
2607:ff80::/36RADBNo 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.