Network · data from 2026-11-12
AS399331 Connect 2 First Internet, LLC
Registry name: CONNECT2FIRST-LLC - Connect 2 First Internet, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS399331, 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.
| 2606:25c0:8019::/48 | Valid | Nonecovered by 2606:25c0::/32 | 634 100% |
| 167.104.196.0/24 | Valid | Nonecovered by 167.104.196.0/22 | 2 0%low visibility |
| 64.127.132.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 64.127.136.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 64.127.137.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 66.220.60.0/23 | Valid | RIR databaseARIN, RADB | 671 100% |
| 174.136.244.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 174.136.244.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 174.136.245.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 192.135.142.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 206.223.148.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 64.127.138.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 66.220.59.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 64.127.133.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 64.127.139.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 206.223.148.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 206.223.150.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 64.127.132.0/24 | Valid | RIR databaseARIN, RADB | 668 99% |
| 64.127.134.0/24 | Valid | RIR databaseARIN, RADB | 668 99% |
| 174.136.246.0/24 | Valid | RIR databaseARIN, RADB | 668 99% |
| 2606:25c0::/32 | Valid | RIR databaseARIN, RADB | 635 100% |
| 174.136.247.0/24 | Valid | RIR databaseARIN, RADB | 200 30% |
| 167.104.196.0/22 | Valid | RIR databaseARIN, RADB | 3 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS399331: AS399331:AS-CONE. 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 (AS399331 isn't in the set, or no route object for AS399331 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 | AS399331 in it | Not covered |
|---|---|---|---|---|---|
| AS399331:AS-CONE | RADB | 3 | 1 | Yes | 0 |
| ARIN (also) | 3 | 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 8 are in fix.csv.
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2606:25c0:8019::/48 | No route object for it. A route object for 2606:25c0::/32 with origin AS399331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399331 in the RIR database for the space. |
| Route object: none | 167.104.196.0/24 | No route object for it. A route object for 167.104.196.0/22 with origin AS399331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399331 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS399331 whose prefix no peer sees AS399331 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.127.135.0/24 | ARIN, RADB | Valid |
| 64.127.136.0/24 | ARIN, RADB | Valid |
| 66.220.60.0/24 | ARIN, RADB | Valid |
| 66.220.61.0/24 | ARIN, RADB | Valid |
| 206.223.149.0/24 | ARIN, RADB | Valid |
| 206.223.151.0/24 | ARIN, 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.