bgpreport

Network · data from 2026-11-12

AS36374 Stellar Association

Registry name: STELLAR-ASSOCIATION - Stellar Association, LLC, US · PeeringDB

17IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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 AS36374, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS36374, 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.
66.234.112.0/20 Valid RIR databaseARIN 671 100% 68
67.230.224.0/19 Valid RIR databaseARIN 671 100% 68
69.42.224.0/19 Valid RIR databaseARIN 671 100% 68
72.18.118.0/23 Valid RIR databaseARIN, RADB 671 100% 68
147.185.100.0/22 Valid RIR databaseARIN, RADB 671 100% 68
152.65.128.0/19 Valid RIR databaseARIN 671 100% 68
162.211.40.0/22 Valid RIR databaseARIN 671 100% 68
162.245.24.0/22 Valid RIR databaseARIN 671 100% 68
172.110.224.0/20 Valid RIR databaseARIN 671 100% 68
173.224.32.0/20 Valid RIR databaseARIN 671 100% 68
192.136.158.0/23 Valid RIR databaseARIN 671 100% 68
192.210.42.0/23 Valid RIR databaseARIN 671 100% 68
198.13.76.0/22 Valid RIR databaseARIN 671 100% 68
199.30.96.0/21 Valid RIR databaseARIN 671 100% 68
206.183.176.0/20 Valid RIR databaseARIN 671 100% 68
216.122.96.0/21 Valid RIR databaseARIN 671 100% 68
216.168.80.0/20 Valid RIR databaseARIN 671 100% 68
2604:4200::/32 Valid RIR databaseARIN 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS36374: AS-STELLAR-ASSOCIATION. 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 (AS36374 isn't in the set, or no route object for AS36374 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 objectsAS36374 in itNot covered
AS-STELLAR-ASSOCIATION ARIN 11180 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 AS36374 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.