Network · data from 2026-11-12
AS1426 TenSpire
Registry name: TENSPIRE-NETWORK-1426 - TenSpire Network, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS1426, 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.
| 104.204.252.0/24 | Valid | Other origin onlycovered by 104.204.252.0/23 | 2 0%low visibility |
| 104.204.253.0/24 | Valid | Other origin onlycovered by 104.204.252.0/23 | 2 0%low visibility |
| 104.204.252.0/23 | Valid | RIR databaseARIN | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS1426: ARIN::AS-TENSPIRE. 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 (AS1426 isn't in the set, or no route object for AS1426 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 | AS1426 in it | Not covered |
|---|---|---|---|---|---|
| ARIN::AS-TENSPIRE | ARIN | 7 | 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 7 are in fix.csv.
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 104.204.252.0/24 | Route objects for it name AS29798. A route object for 104.204.252.0/23 with origin AS1426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1426 in the RIR database for the space. |
| Route object: none | 104.204.253.0/24 | Route objects for it name AS29798. A route object for 104.204.252.0/23 with origin AS1426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1426 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS1426 whose prefix no peer sees AS1426 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.163.223.0/24 | ARIN | Valid |
| 103.246.186.0/24 | ARIN | Valid |
| 123.100.246.0/24 | ARIN | Valid |
| 203.11.72.0/24 | ARIN | Valid |
| 2620:ca:a000::/48 | 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.