Network · data from 2026-11-12
AS11080 Yellowknife Wireless Company
Registry name: YKWC - Yellowknife Wireless Company, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11080, 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.
| 69.88.226.0/23 | No ROA | Other IRR onlyRADB | 670 100% |
| 130.44.26.0/23 | No ROA | Other IRR onlyALTDB, RADB | 670 100% |
| 199.68.200.0/21 | No ROA | Other IRR onlyALTDB, NTTCOM, RADB | 670 100% |
| 204.17.205.0/24 | No ROA | Other IRR onlyALTDB, NTTCOM, RADB | 670 100% |
| 204.29.139.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 204.80.187.0/24 | No ROA | Other IRR onlyALTDB, NTTCOM | 670 100% |
| 206.223.111.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 2602:ffc0::/36 | No ROA | Other IRR onlyALTDB, NTTCOM | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS11080: ALTDB::AS11080:AS-ALL. 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 (AS11080 isn't in the set, or no route object for AS11080 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 | AS11080 in it | Not covered |
|---|---|---|---|---|---|
| ALTDB::AS11080:AS-ALL | ALTDB1 member set in no database: AS11080:AS-CUSTOMERS | 1 | 1 | 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 17 are in fix.csv.
- ROA: none8
- Route object: RIR8
- AS-SET: missing member1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 69.88.226.0/23 | No ROA covers it. Add a ROA for AS11080, maxLength 23. |
| Route object: RIR | 69.88.226.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 130.44.26.0/23 | No ROA covers it. Add a ROA for AS11080, maxLength 23. |
| Route object: RIR | 130.44.26.0/23 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 199.68.200.0/21 | No ROA covers it. Add a ROA for AS11080, maxLength 21. |
| Route object: RIR | 199.68.200.0/21 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 204.17.205.0/24 | No ROA covers it. Add a ROA for AS11080, maxLength 24. |
| Route object: RIR | 204.17.205.0/24 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 204.29.139.0/24 | No ROA covers it. Add a ROA for AS11080, maxLength 24. |
| Route object: RIR | 204.29.139.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 204.80.187.0/24 | No ROA covers it. Add a ROA for AS11080, maxLength 24. |
| Route object: RIR | 204.80.187.0/24 | Route object only in ALTDB, NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 206.223.111.0/24 | No ROA covers it. Add a ROA for AS11080, maxLength 24. |
| Route object: RIR | 206.223.111.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 2602:ffc0::/36 | No ROA covers it. Add a ROA for AS11080, maxLength 36. |
| Route object: RIR | 2602:ffc0::/36 | Route object only in ALTDB, NTTCOM. Add it in the RIR database for the space. |
| AS-SET: missing member | ALTDB::AS11080:AS-ALL | AS11080:AS-ALL (ALTDB) lists AS11080:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Every route object with origin AS11080 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.