Network · data from 2026-11-12
AS25798 NTS Huntsville
Registry name: NTS-HUNTSVILLE-01 - Vexus Fiber, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25798, 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.
| 38.158.134.0/23 | No ROA | Other origin onlycovered by 38.158.128.0/18 | 673 100% |
| 38.172.108.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 72.59.244.0/24 | Valid | Nonecovered by 72.59.244.0/22 | 670 100% |
| 72.59.245.0/24 | Valid | Nonecovered by 72.59.244.0/22 | 670 100% |
| 72.59.244.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS25798: AS-25798. 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 (AS25798 isn't in the set, or no route object for AS25798 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 | AS25798 in it | Not covered |
|---|---|---|---|---|---|
| AS-25798 | RADB | 0 | 1 | No | 5 |
| ARIN (also) | 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 11 are in fix.csv.
- ROA: none2
- Route object: none3
- Route object: RIR1
- AS-SET: own ASN1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.158.134.0/23 | No ROA covers it. Add a ROA for AS25798, maxLength 23. |
| Route object: none | 38.158.134.0/23 | Route objects for it name AS35924. A route object for 38.158.128.0/18 with origin AS25798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25798 in the RIR database for the space. |
| ROA: none | 38.172.108.0/24 | No ROA covers it. Add a ROA for AS25798, maxLength 24. |
| Route object: RIR | 38.172.108.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 72.59.244.0/24 | No route object for it. A route object for 72.59.244.0/22 with origin AS25798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25798 in the RIR database for the space. |
| Route object: none | 72.59.245.0/24 | No route object for it. A route object for 72.59.244.0/22 with origin AS25798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25798 in the RIR database for the space. |
| AS-SET: own ASN | AS-25798 | AS25798 isn't in AS-25798 (RADB) once expanded. Add AS25798 to it. |
Route objects not announced
Route objects with origin AS25798 whose prefix no peer sees AS25798 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.158.128.0/18 | RADB | No ROA |
| 38.158.134.0/24 | RADB | No ROA |
| 38.172.64.0/18 | RADB | No ROA |
| 65.223.77.0/24 | 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.