Network · data from 2026-11-12
AS46091 FGL Telecom
Registry name: FGLTEL - FGLTEL Inc., CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46091, 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.
| 165.140.32.0/22 | No ROA | None | 2 0%low visibility |
| 104.249.140.0/23 | Valid | Nonecovered by 104.249.140.0/22 | 673 100% |
| 172.111.60.0/24 | Valid | Nonecovered by 172.111.60.0/22 | 673 100% |
| 172.111.61.0/24 | Valid | Nonecovered by 172.111.60.0/22 | 673 100% |
| 172.111.62.0/24 | Valid | Nonecovered by 172.111.60.0/22 | 673 100% |
| 172.111.63.0/24 | Valid | Nonecovered by 172.111.60.0/22 | 673 100% |
| 45.42.184.0/24 | Valid | Nonecovered by 45.42.184.0/22 | 672 100% |
| 45.42.185.0/24 | Valid | Nonecovered by 45.42.184.0/22 | 672 100% |
| 45.42.187.0/24 | Valid | Nonecovered by 45.42.184.0/22 | 672 100% |
| 2605:de40:100::/40 | Valid | Nonecovered by 2605:de40::/32 | 634 100% |
| 2605:de40:200::/40 | Valid | Nonecovered by 2605:de40::/32 | 634 100% |
| 2605:de40:300::/40 | Valid | Nonecovered by 2605:de40::/32 | 634 100% |
| 2605:de40:400::/40 | Valid | Nonecovered by 2605:de40::/32 | 634 100% |
| 2605:de40:500::/40 | Valid | Nonecovered by 2605:de40::/32 | 634 100% |
| 2605:de40:600::/40 | Valid | Nonecovered by 2605:de40::/32 | 634 100% |
| 2605:de40:700::/40 | Valid | Nonecovered by 2605:de40::/32 | 634 100% |
| 2605:de40:800::/40 | Valid | Nonecovered by 2605:de40::/32 | 634 100% |
| 2605:de40:900::/40 | Valid | Nonecovered by 2605:de40::/32 | 634 100% |
| 2605:de40:1000::/40 | Valid | Nonecovered by 2605:de40::/32 | 634 100% |
| 45.42.186.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.42.184.0/22 | Valid | RIR databaseARIN | 673 100% |
| 104.249.140.0/22 | Valid | RIR databaseARIN | 673 100% |
| 104.249.140.0/24 | Valid | RIR databaseARIN | 673 100% |
| 104.249.141.0/24 | Valid | RIR databaseARIN | 673 100% |
| 104.249.142.0/24 | Valid | RIR databaseARIN | 673 100% |
| 104.249.143.0/24 | Valid | RIR databaseARIN | 673 100% |
| 165.140.32.0/24 | Valid | RIR databaseARIN | 673 100% |
| 165.140.33.0/24 | Valid | RIR databaseARIN | 673 100% |
| 172.111.60.0/22 | Valid | RIR databaseARIN | 673 100% |
| 216.24.34.0/24 | Valid | RIR databaseARIN | 673 100% |
| 2605:de40::/32 | Valid | RIR databaseARIN | 634 100% |
| 165.140.34.0/24 | Valid | RIR databaseARIN | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS46091: AS-FGLTEL. 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 (AS46091 isn't in the set, or no route object for AS46091 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 | AS46091 in it | Not covered |
|---|---|---|---|---|---|
| AS-FGLTEL | ARINlists itself further down | 3 | 3 | 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 22 are in fix.csv.
- ROA: none1
- Route object: none19
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 165.140.32.0/22 | No ROA covers it. Add a ROA for AS46091, maxLength 22. |
| Route object: none | 165.140.32.0/22 | No route object for it. Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 104.249.140.0/23 | No route object for it. A route object for 104.249.140.0/22 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 172.111.60.0/24 | No route object for it. A route object for 172.111.60.0/22 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 172.111.61.0/24 | No route object for it. A route object for 172.111.60.0/22 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 172.111.62.0/24 | No route object for it. A route object for 172.111.60.0/22 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 172.111.63.0/24 | No route object for it. A route object for 172.111.60.0/22 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 45.42.184.0/24 | No route object for it. A route object for 45.42.184.0/22 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 45.42.185.0/24 | No route object for it. A route object for 45.42.184.0/22 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 45.42.187.0/24 | No route object for it. A route object for 45.42.184.0/22 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 2605:de40:100::/40 | No route object for it. A route object for 2605:de40::/32 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 2605:de40:200::/40 | No route object for it. A route object for 2605:de40::/32 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 2605:de40:300::/40 | No route object for it. A route object for 2605:de40::/32 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 2605:de40:400::/40 | No route object for it. A route object for 2605:de40::/32 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 2605:de40:500::/40 | No route object for it. A route object for 2605:de40::/32 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 2605:de40:600::/40 | No route object for it. A route object for 2605:de40::/32 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 2605:de40:700::/40 | No route object for it. A route object for 2605:de40::/32 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 2605:de40:800::/40 | No route object for it. A route object for 2605:de40::/32 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 2605:de40:900::/40 | No route object for it. A route object for 2605:de40::/32 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: none | 2605:de40:1000::/40 | No route object for it. A route object for 2605:de40::/32 with origin AS46091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46091 in the RIR database for the space. |
| Route object: RIR | 45.42.186.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46091 whose prefix no peer sees AS46091 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 165.140.35.0/24 | 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.