Network · data from 2026-11-12
AS41343 TRIUNFOTEL-ASN Free Technologies Excom S.L.
Registry name: TRIUNFOTEL-ASN Free Technologies Excom S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41343, 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.
| 185.111.0.0/22 | Valid | None | 672 100% |
| 185.110.212.0/24 | Valid | Other origin onlycovered by 185.110.212.0/22 | 670 100% |
| 185.111.0.0/24 | Valid | Nonecovered by 185.111.0.0/23 | 668 99% |
| 185.111.1.0/24 | Valid | Nonecovered by 185.111.0.0/23 | 668 99% |
| 185.110.212.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 185.110.215.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.110.214.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.40.36.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS41343 isn't in PeeringDB, where networks name their AS-SET.
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 31 are in fix.csv.
- Route object: none4
- Route object: not announced27
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.111.0.0/22 | No route object for it. Add a route object with origin AS41343 in the RIR database for the space. |
| Route object: none | 185.110.212.0/24 | Route objects for it name AS34471. A route object for 185.110.212.0/22 with origin AS41343 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41343 in the RIR database for the space. |
| Route object: none | 185.111.0.0/24 | No route object for it. A route object for 185.111.0.0/23 with origin AS41343 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41343 in the RIR database for the space. |
| Route object: none | 185.111.1.0/24 | No route object for it. A route object for 185.111.0.0/23 with origin AS41343 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41343 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS41343 whose prefix no peer sees AS41343 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.29.192.0/21 | RIPE | Invalid: origin |
| 89.29.192.0/24 | RIPE | Valid |
| 89.29.193.0/24 | RIPE | Valid |
| 89.29.194.0/24 | RIPE | Valid |
| 89.29.195.0/24 | RIPE | Valid |
| 89.29.196.0/24 | RIPE | Valid |
| 89.29.197.0/24 | RIPE | Valid |
| 89.29.198.0/24 | RIPE | Valid |
| 89.29.199.0/24 | RIPE | Valid |
| 89.29.200.0/23 | RIPE | Valid |
| 89.29.200.0/24 | RIPE | Invalid: maxLength |
| 89.29.201.0/24 | RIPE | Invalid: maxLength |
| 89.29.202.0/24 | RIPE | Valid |
| 89.29.204.0/23 | RIPE | No ROA |
| 89.29.204.0/24 | RIPE | Valid |
| 89.29.205.0/24 | RIPE | Valid |
| 89.29.226.0/24 | RIPE | Valid |
| 89.29.227.0/24 | RIPE | Valid |
| 89.29.228.0/24 | RIPE | Valid |
| 185.110.213.0/24 | RIPE | Valid |
| 185.111.0.0/23 | RIPE | Valid |
| 185.111.2.0/24 | RIPE | Valid |
| 185.111.3.0/24 | RIPE | Valid |
| 213.181.70.0/23 | RIPE | Valid |
| 213.181.70.0/24 | RIPE | Valid |
| 213.181.71.0/24 | RIPE | Valid |
| 2a00:4b80:7::/48 | RIPE | 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.