Network · data from 2026-11-12
AS19406 TWRS-MA - Towerstream I, Inc.
Registry name: TWRS-MA - Towerstream I, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19406, 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.
| 192.74.137.0/24 | No ROA | None | 673 100% |
| 2604:f400:5::/48 | No ROA | None | 2 0%low visibility |
| 2604:f400:2800::/37 | No ROA | None | 2 0%low visibility |
| 64.119.128.0/19 | No ROA | RIR databaseARIN | 673 100% |
| 66.228.64.0/20 | No ROA | RIR databaseARIN | 673 100% |
| 69.38.144.0/20 | No ROA | RIR databaseARIN | 673 100% |
| 69.38.176.0/22 | No ROA | RIR databaseARIN | 673 100% |
| 72.46.160.0/21 | No ROA | RIR databaseARIN | 673 100% |
| 72.46.168.0/22 | No ROA | RIR databaseARIN | 673 100% |
| 216.57.82.0/23 | No ROA | RIR databaseARIN | 673 100% |
| 216.57.84.0/22 | No ROA | RIR databaseARIN | 673 100% |
| 216.57.88.0/21 | No ROA | RIR databaseARIN | 673 100% |
AS-SET
AS19406 isn't in PeeringDB, where networks name their AS-SET.
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 23 are in fix.csv.
- ROA: none12
- Route object: none3
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.74.137.0/24 | No ROA covers it. Add a ROA for AS19406, maxLength 24. |
| Route object: none | 192.74.137.0/24 | No route object for it. Add a route object with origin AS19406 in the RIR database for the space. |
| ROA: none | 2604:f400:5::/48 | No ROA covers it. Add a ROA for AS19406, maxLength 48. |
| Route object: none | 2604:f400:5::/48 | No route object for it. Add a route object with origin AS19406 in the RIR database for the space. |
| ROA: none | 2604:f400:2800::/37 | No ROA covers it. Add a ROA for AS19406, maxLength 37. |
| Route object: none | 2604:f400:2800::/37 | No route object for it. Add a route object with origin AS19406 in the RIR database for the space. |
| ROA: none | 64.119.128.0/19 | No ROA covers it. Add a ROA for AS19406, maxLength 19. |
| ROA: none | 66.228.64.0/20 | No ROA covers it. Add a ROA for AS19406, maxLength 20. |
| ROA: none | 69.38.144.0/20 | No ROA covers it. Add a ROA for AS19406, maxLength 20. |
| ROA: none | 69.38.176.0/22 | No ROA covers it. Add a ROA for AS19406, maxLength 22. |
| ROA: none | 72.46.160.0/21 | No ROA covers it. Add a ROA for AS19406, maxLength 21. |
| ROA: none | 72.46.168.0/22 | No ROA covers it. Add a ROA for AS19406, maxLength 22. |
| ROA: none | 216.57.82.0/23 | No ROA covers it. Add a ROA for AS19406, maxLength 23. |
| ROA: none | 216.57.84.0/22 | No ROA covers it. Add a ROA for AS19406, maxLength 22. |
| ROA: none | 216.57.88.0/21 | No ROA covers it. Add a ROA for AS19406, maxLength 21. |
Route objects not announced
Route objects with origin AS19406 whose prefix no peer sees AS19406 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.117.234.0/24 | RADB | No ROA |
| 192.1.118.0/24 | RADB | No ROA |
| 192.207.56.0/24 | RADB | No ROA |
| 192.207.57.0/24 | RADB | No ROA |
| 192.207.58.0/24 | RADB | No ROA |
| 208.131.216.0/22 | RADB | No ROA |
| 208.131.220.0/23 | RADB | No ROA |
| 208.156.124.0/22 | 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.