Network · data from 2026-11-12
AS19261 aspStation
Registry name: ASPSTATION - aspStation, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19261, 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.207.128.0/20 | No ROA | Other IRR onlyRADB | 671 100% |
| 198.144.32.0/20 | No ROA | Other IRR onlyRADB | 671 100% |
| 205.167.80.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS19261: AS19261 AS46619. 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 (AS19261 isn't in the set, or no route object for AS19261 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 | AS19261 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS19261 | A single AS number, not a set: AS19261 (this network), 5 route objects. | |||||
| AS46619 | A single AS number, not a set: AS46619, 3 route objects. | |||||
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: none3
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 66.207.128.0/20 | No ROA covers it. Add a ROA for AS19261, maxLength 20. |
| Route object: RIR | 66.207.128.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 198.144.32.0/20 | No ROA covers it. Add a ROA for AS19261, maxLength 20. |
| Route object: RIR | 198.144.32.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 205.167.80.0/23 | No ROA covers it. Add a ROA for AS19261, maxLength 23. |
| Route object: RIR | 205.167.80.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19261 whose prefix no peer sees AS19261 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.158.19.0/24 | RADB | No ROA |
| 204.187.255.0/24 | RADB | 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.