Network · data from 2026-11-12
AS46849 Texas Lone Star Network
Registry name: TLSN-TX - TEXAS LONE STAR NETWORK, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46849, 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.
| 65.116.14.0/23 | No ROA | None | 670 100% |
| 65.116.14.0/24 | No ROA | None | 670 100% |
| 216.207.56.0/24 | No ROA | None | 670 100% |
| 65.116.15.0/24 | No ROA | None | 667 99% |
| 192.207.55.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 198.48.40.0/22 | No ROA | RIR databaseARIN | 670 100% |
| 2605:300::/32 | No ROA | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS46849: AS-AS46849. 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 (AS46849 isn't in the set, or no route object for AS46849 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 | AS46849 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-AS46849 | In no IRR database read today. | |||||
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 12 are in fix.csv.
- ROA: none7
- Route object: none4
- AS-SET: not found1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 65.116.14.0/23 | No ROA covers it. Add a ROA for AS46849, maxLength 23. |
| Route object: none | 65.116.14.0/23 | No route object for it. Add a route object with origin AS46849 in the RIR database for the space. |
| ROA: none | 65.116.14.0/24 | No ROA covers it. Add a ROA for AS46849, maxLength 24. |
| Route object: none | 65.116.14.0/24 | No route object for it. Add a route object with origin AS46849 in the RIR database for the space. |
| ROA: none | 216.207.56.0/24 | No ROA covers it. Add a ROA for AS46849, maxLength 24. |
| Route object: none | 216.207.56.0/24 | No route object for it. Add a route object with origin AS46849 in the RIR database for the space. |
| ROA: none | 65.116.15.0/24 | No ROA covers it. Add a ROA for AS46849, maxLength 24. |
| Route object: none | 65.116.15.0/24 | No route object for it. Add a route object with origin AS46849 in the RIR database for the space. |
| ROA: none | 192.207.55.0/24 | No ROA covers it. Add a ROA for AS46849, maxLength 24. |
| ROA: none | 198.48.40.0/22 | No ROA covers it. Add a ROA for AS46849, maxLength 22. |
| ROA: none | 2605:300::/32 | No ROA covers it. Add a ROA for AS46849, maxLength 32. |
| AS-SET: not found | AS-AS46849 | PeeringDB names AS-AS46849; no IRR database read has it. |
Route objects not announced
Every route object with origin AS46849 is announced.
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.