Network · data from 2026-11-12
AS20394 Rainier Connect
Registry name: MASHELL-TELECOM - Rainier Connect, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20394, 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.
| 205.134.216.0/24 | No ROA | Nonecovered by 205.134.192.0/19 | 673 100% |
| 2604:d340::/32 | No ROA | Other origin only | 634 100% |
| 205.134.192.0/19 | No ROA | Other IRR onlyRADB | 673 100% |
| 216.177.224.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 2604:b100::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 69.10.192.0/20 | Valid | RIR databaseARIN, RADB | 673 100% |
| 74.50.192.0/20 | Valid | RIR databaseARIN, RADB | 673 100% |
| 69.10.208.0/20 | Valid | RIR databaseARIN, RADB | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS20394: AS-20394-CUSTOMERS. 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 (AS20394 isn't in the set, or no route object for AS20394 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 | AS20394 in it | Not covered |
|---|---|---|---|---|---|
| AS-20394-CUSTOMERS | RADB2 member sets in no database: AS-COIXIA, AS208753:AS-DANGELO | 24 | 9 | Yes | 1 |
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 15 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: RIR3
- AS-SET: missing member2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 205.134.216.0/24 | No ROA covers it. Add a ROA for AS20394, maxLength 24. |
| Route object: none | 205.134.216.0/24 | No route object for it. A route object for 205.134.192.0/19 with origin AS20394 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20394 in the RIR database for the space. |
| ROA: none | 2604:d340::/32 | No ROA covers it. Add a ROA for AS20394, maxLength 32. |
| Route object: none | 2604:d340::/32 | Route objects for it name AS14677. Add a route object with origin AS20394 in the RIR database for the space. |
| ROA: none | 205.134.192.0/19 | No ROA covers it. Add a ROA for AS20394, maxLength 19. |
| Route object: RIR | 205.134.192.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 216.177.224.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2604:b100::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-20394-CUSTOMERS | AS-20394-CUSTOMERS (RADB) lists AS-COIXIA; no IRR database read has it. |
| AS-SET: missing member | AS-20394-CUSTOMERS | AS-20394-CUSTOMERS (RADB) lists AS208753:AS-DANGELO; no IRR database read has it. |
Route objects not announced
Route objects with origin AS20394 whose prefix no peer sees AS20394 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 69.10.192.0/19 | RADB | Valid |
| 69.10.210.0/23 | RADB | Valid |
| 69.10.212.0/22 | RADB | Valid |
| 74.50.192.0/24 | RADB | Valid |
| 191.45.64.0/18 | ARIN | Valid |
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.