Network · data from 2026-11-12
AS19331 Twin Lakes
Registry name: TWIN-LAKES - Twin Lakes Telephone Cooperative Corporation, US · PeeringDB
39IPv4 routes
97.4% RPKI valid · 59.0% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
16 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
51Route objects not announced
registered with origin AS19331, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS19331, 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.
| 64.53.2.0/23 | No ROA | Other IRR onlyALTDB | 670 100% |
| 149.149.0.0/17 | Valid | Nonecovered by 149.149.0.0/16 | 673 100% |
| 149.149.128.0/17 | Valid | Nonecovered by 149.149.0.0/16 | 673 100% |
| 67.212.248.0/21 | Valid | Nonecovered by 67.212.240.0/20 | 670 100% |
| 135.129.192.0/20 | Valid | Nonecovered by 135.129.192.0/19 | 139 21% |
| 63.135.176.0/21 | Valid | Nonecovered by 63.135.176.0/20 | 136 20% |
| 63.135.184.0/21 | Valid | Nonecovered by 63.135.176.0/20 | 136 20% |
| 67.212.240.0/21 | Valid | Nonecovered by 67.212.240.0/20 | 136 20% |
| 69.55.112.0/21 | Valid | Nonecovered by 69.55.112.0/20 | 136 20% |
| 148.59.248.0/22 | Valid | Nonecovered by 148.59.248.0/21 | 134 20% |
| 148.59.252.0/22 | Valid | Nonecovered by 148.59.248.0/21 | 134 20% |
| 148.64.52.0/22 | Valid | Nonecovered by 148.64.48.0/21 | 134 20% |
| 162.251.56.0/23 | Valid | Nonecovered by 162.251.56.0/22 | 134 20% |
| 192.81.104.0/23 | Valid | Nonecovered by 192.81.104.0/22 | 134 20% |
| 192.81.106.0/23 | Valid | Nonecovered by 192.81.104.0/22 | 134 20% |
| 199.33.96.0/22 | Valid | Nonecovered by 199.33.96.0/21 | 134 20% |
| 199.33.100.0/22 | Valid | Nonecovered by 199.33.96.0/21 | 134 20% |
| 135.129.192.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 148.170.96.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 169.150.160.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 67.212.240.0/20 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 69.55.112.0/20 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 74.118.44.0/22 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 148.59.248.0/21 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 148.64.48.0/21 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 150.252.160.0/19 | Valid | Other IRR onlyRADB | 671 100% |
| 162.251.56.0/22 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 168.245.160.0/20 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 192.80.204.0/23 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 192.81.104.0/22 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 192.199.184.0/21 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 199.33.96.0/21 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 199.102.180.0/22 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 199.187.200.0/21 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 199.195.208.0/22 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 63.135.176.0/20 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 668 99% |
| 149.106.32.0/19 | Valid | Other IRR onlyRADB | 668 99% |
| 2606:6500::/28 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 632 99% |
| 91.85.160.0/19 | Valid | RIR databaseARIN, RADB | 671 100% |
| 149.64.225.0/24 | Valid | RIR databaseARIN, RADB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS19331: AS19331:AS-TWINLAKES. 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 (AS19331 isn't in the set, or no route object for AS19331 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 | AS19331 in it | Not covered |
|---|---|---|---|---|---|
| AS19331:AS-TWINLAKES | RADB | 9 | 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 90 are in fix.csv.
- ROA: none1
- Route object: none16
- Route object: RIR22
- Route object: not announced51
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.53.2.0/23 | No ROA covers it. Add a ROA for AS19331, maxLength 23. |
| Route object: RIR | 64.53.2.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: none | 149.149.0.0/17 | No route object for it. A route object for 149.149.0.0/16 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 149.149.128.0/17 | No route object for it. A route object for 149.149.0.0/16 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 67.212.248.0/21 | No route object for it. A route object for 67.212.240.0/20 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 135.129.192.0/20 | No route object for it. A route object for 135.129.192.0/19 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 63.135.176.0/21 | No route object for it. A route object for 63.135.176.0/20 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 63.135.184.0/21 | No route object for it. A route object for 63.135.176.0/20 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 67.212.240.0/21 | No route object for it. A route object for 67.212.240.0/20 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 69.55.112.0/21 | No route object for it. A route object for 69.55.112.0/20 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 148.59.248.0/22 | No route object for it. A route object for 148.59.248.0/21 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 148.59.252.0/22 | No route object for it. A route object for 148.59.248.0/21 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 148.64.52.0/22 | No route object for it. A route object for 148.64.48.0/21 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 162.251.56.0/23 | No route object for it. A route object for 162.251.56.0/22 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 192.81.104.0/23 | No route object for it. A route object for 192.81.104.0/22 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 192.81.106.0/23 | No route object for it. A route object for 192.81.104.0/22 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 199.33.96.0/22 | No route object for it. A route object for 199.33.96.0/21 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: none | 199.33.100.0/22 | No route object for it. A route object for 199.33.96.0/21 with origin AS19331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19331 in the RIR database for the space. |
| Route object: RIR | 135.129.192.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.170.96.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 169.150.160.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 67.212.240.0/20 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 69.55.112.0/20 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 74.118.44.0/22 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.59.248.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.64.48.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 150.252.160.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 162.251.56.0/22 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.245.160.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.80.204.0/23 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.81.104.0/22 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.184.0/21 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.33.96.0/21 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.102.180.0/22 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.187.200.0/21 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.195.208.0/22 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 63.135.176.0/20 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 149.106.32.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:6500::/28 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19331 whose prefix no peer sees AS19331 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.53.103.0/24 | RADB | No ROA |
| 149.149.0.0/16 | RADB | Valid |
| 168.245.162.0/24 | RADB | Valid |
| 192.19.184.0/21 | ALTDB | No ROA |
| 204.116.9.0/24 | ALTDB, NTTCOM | No ROA |
| 204.116.10.0/24 | ALTDB | No ROA |
| 204.116.29.0/24 | ALTDB | No ROA |
| 204.116.98.0/23 | ALTDB | No ROA |
| 204.116.99.0/24 | ALTDB | No ROA |
| 204.116.108.0/24 | ALTDB | No ROA |
| 204.116.112.0/23 | ALTDB | No ROA |
| 204.116.119.0/24 | ALTDB, NTTCOM | No ROA |
| 204.116.127.0/24 | ALTDB, NTTCOM | No ROA |
| 204.116.135.0/24 | ALTDB, NTTCOM | No ROA |
| 204.116.136.0/24 | ALTDB, NTTCOM | No ROA |
| 204.116.152.0/21 | ALTDB, NTTCOM | No ROA |
| 204.116.152.0/24 | ALTDB | No ROA |
| 204.116.154.0/24 | ALTDB | No ROA |
| 204.116.155.0/24 | ALTDB | No ROA |
| 204.116.156.0/24 | ALTDB | No ROA |
| 204.116.160.0/24 | ALTDB, NTTCOM | No ROA |
| 204.116.170.0/23 | ALTDB | No ROA |
| 204.116.179.0/24 | ALTDB | No ROA |
| 204.116.255.0/24 | ALTDB, NTTCOM | No ROA |
| 206.74.2.0/24 | ALTDB | No ROA |
| 206.74.21.0/24 | ALTDB | No ROA |
| 206.74.22.0/24 | ALTDB | No ROA |
| 206.74.54.0/24 | ALTDB | No ROA |
| 206.74.57.0/24 | ALTDB | No ROA |
| 206.74.73.0/24 | ALTDB | No ROA |
| 206.74.74.0/23 | NTTCOM | No ROA |
| 206.74.74.0/24 | ALTDB | No ROA |
| 206.74.75.0/24 | ALTDB | No ROA |
| 206.74.76.0/24 | ALTDB, NTTCOM | No ROA |
| 207.144.1.0/24 | ALTDB | No ROA |
| 207.144.39.0/24 | ALTDB, NTTCOM | No ROA |
| 207.144.40.0/24 | ALTDB, NTTCOM | No ROA |
| 207.144.43.0/24 | ALTDB, NTTCOM | No ROA |
| 207.144.65.0/24 | ALTDB, NTTCOM | No ROA |
| 207.144.66.0/24 | ALTDB, NTTCOM | No ROA |
| 207.144.71.0/24 | ALTDB, NTTCOM | No ROA |
| 207.144.77.0/24 | ALTDB | No ROA |
| 207.144.112.0/24 | ALTDB | No ROA |
| 207.144.128.0/23 | ALTDB | No ROA |
| 207.144.128.0/24 | ALTDB | No ROA |
| 207.144.129.0/24 | ALTDB | No ROA |
| 207.144.130.0/24 | ALTDB | No ROA |
| 207.144.132.0/24 | ALTDB | No ROA |
| 207.144.166.0/24 | ALTDB | No ROA |
| 207.144.196.0/23 | ALTDB | No ROA |
| 207.144.204.0/23 | ALTDB | 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.