Network · data from 2026-11-12
AS394144 LTY CONNECT
Registry name: LTYCONNECT - LTY CONNECT, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS394144, 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.
| 45.82.236.0/23 | Valid | None | 670 100% |
| 2a0e:7581::/32 | Valid | Other origin onlycovered by 2a0e:7580::/29 | 634 100% |
| 23.145.160.0/24 | Valid | RIR databaseALTDB, ARIN, RADB | 670 100% |
| 23.153.24.0/24 | Valid | RIR databaseARIN | 670 100% |
| 130.51.127.0/24 | Valid | RIR databaseARIN | 670 100% |
| 155.103.44.0/23 | Valid | RIR databaseARIN | 670 100% |
| 192.234.79.0/24 | Valid | RIR databaseALTDB, ARIN, RADB | 670 100% |
| 199.21.15.0/24 | Valid | RIR databaseALTDB, ARIN | 670 100% |
| 2602:ff7a::/32 | Valid | RIR databaseALTDB, ARIN | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS394144: AS-LTYCONNECT. 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 (AS394144 isn't in the set, or no route object for AS394144 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 | AS394144 in it | Not covered |
|---|---|---|---|---|---|
| AS-LTYCONNECT | ARIN | 3 | 2 | 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 8 are in fix.csv.
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.82.236.0/23 | No route object for it. Add a route object with origin AS394144 in the RIR database for the space. |
| Route object: none | 2a0e:7581::/32 | Route objects for it name AS208830. A route object for 2a0e:7580::/29 with origin AS394144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394144 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS394144 whose prefix no peer sees AS394144 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.152.56.0/24 | ARIN | Valid |
| 44.127.16.0/20 | ALTDB, RADB | No ROA |
| 198.135.179.0/24 | ARIN | Valid |
| 2602:2cd::/36 | ARIN | Valid |
| 2602:ff7a:ffd::/48 | ARIN | Invalid: maxLength |
| 2a0e:7580::/29 | RADB | 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.