Network · data from 2026-11-12

AS36829 Winstri

Registry name: AS-WINSTRI - Winstri Corporation, US · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object

6IPv6 routes 83.3% RPKI valid · 83.3% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS36829, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS36829, 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:fc64:a00::/48	No ROA	Nonecovered by 2602:fc64::/32	635 100%	67
172.111.56.0/24	Valid	RIR databaseARIN	673 100%	67
209.142.101.0/24	Valid	RIR databaseARIN	673 100%	67
104.156.149.0/24	Valid	RIR databaseARIN	672 100%	70
141.195.98.0/24	Valid	RIR databaseARIN	672 100%	70
141.195.99.0/24	Valid	RIR databaseARIN	672 100%	70
104.156.148.0/24	Valid	RIR databaseARIN	670 100%	67
206.83.151.0/24	Valid	RIR databaseARIN	670 100%	67
2602:fc64:a000::/48	Valid	RIR databaseARIN	636 100%	67
2602:fc64:a001::/48	Valid	RIR databaseARIN	636 100%	67
2602:fc64:ca00::/48	Valid	RIR databaseARIN	636 100%	67
2602:fc64:ca10::/48	Valid	RIR databaseARIN	635 100%	68
2602:fc64:ce00::/48	Valid	RIR databaseARIN	635 100%	67

AS-SET

PeeringDB's irr_as_set for AS36829: AS-WINSTRI. 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 (AS36829 isn't in the set, or no route object for AS36829 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.

Name	Database	ASNs	Sets	Route objects	AS36829 in it	Not covered
AS-WINSTRI	ARIN	1	1	13	Yes	0

Name

Database

ASNs

Sets

Route objects

AS36829 in it

Not covered

AS-WINSTRI

ARIN

Yes

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

ROA: none1
Route object: none1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2602:fc64:a00::/48	No ROA covers it. Add a ROA for AS36829, maxLength 48.	635 of 636
Route object: none	2602:fc64:a00::/48	No route object for it. A route object for 2602:fc64::/32 with origin AS36829 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36829 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2602:fc64:a00::/48

No ROA covers it. Add a ROA for AS36829, maxLength 48.

635 of 636

Route object: none

2602:fc64:a00::/48

No route object for it. A route object for 2602:fc64::/32 with origin AS36829 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36829 in the RIR database for the space.

635 of 636

Route objects not announced

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


2602:fc64::/32	ARIN	No ROA

2602:fc64::/32

ARIN

No 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.