Network · data from 2026-11-12
AS32621 Minnesota VoIP
Registry name: TCV-511 - Twin City VoIP, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS32621, 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.69.76.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 192.69.77.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 192.69.78.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 198.137.142.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 205.215.193.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 192.69.79.0/24 | No ROA | RIR databaseARIN | 669 99% |
| 2602:ffaa::/36 | No ROA | RIR databaseARIN | 635 100% |
| 216.45.236.0/24 | Valid | None | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS32621: AS-TCVTRANSIT. 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 (AS32621 isn't in the set, or no route object for AS32621 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 | AS32621 in it | Not covered |
|---|---|---|---|---|---|
| AS-TCVTRANSIT | ARIN | 44 | 1 | 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 11 are in fix.csv.
- ROA: none7
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.69.76.0/24 | No ROA covers it. Add a ROA for AS32621, maxLength 24. |
| ROA: none | 192.69.77.0/24 | No ROA covers it. Add a ROA for AS32621, maxLength 24. |
| ROA: none | 192.69.78.0/24 | No ROA covers it. Add a ROA for AS32621, maxLength 24. |
| ROA: none | 198.137.142.0/24 | No ROA covers it. Add a ROA for AS32621, maxLength 24. |
| ROA: none | 205.215.193.0/24 | No ROA covers it. Add a ROA for AS32621, maxLength 24. |
| ROA: none | 192.69.79.0/24 | No ROA covers it. Add a ROA for AS32621, maxLength 24. |
| ROA: none | 2602:ffaa::/36 | No ROA covers it. Add a ROA for AS32621, maxLength 36. |
| Route object: none | 216.45.236.0/24 | No route object for it. Add a route object with origin AS32621 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS32621 whose prefix no peer sees AS32621 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 162.219.164.0/22 | RADB | No ROA |
| 2001:470:91::/48 | ARIN | Valid |
| 2620:116:c000::/44 | 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.