Network · data from 2026-11-12
AS1729 TELIA-TCN Telia Company AB
Registry name: TELIA-TCN Telia Company AB, SE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS1729, 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.
| 192.43.165.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 192.43.169.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 192.121.19.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 131.115.30.0/23 | Valid | Nonecovered by 131.115.0.0/16 | 673 100% |
| 131.115.51.0/24 | Valid | Nonecovered by 131.115.0.0/16 | 673 100% |
| 131.115.80.0/21 | Valid | Nonecovered by 131.115.0.0/16 | 673 100% |
| 131.115.128.0/20 | Valid | Nonecovered by 131.115.0.0/16 | 673 100% |
| 131.115.164.0/23 | Valid | Nonecovered by 131.115.0.0/16 | 673 100% |
| 131.115.192.0/21 | Valid | Nonecovered by 131.115.0.0/16 | 673 100% |
| 131.115.200.0/22 | Valid | Nonecovered by 131.115.0.0/16 | 673 100% |
| 131.115.248.0/21 | Valid | Nonecovered by 131.115.0.0/16 | 673 100% |
| 131.116.1.0/24 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.2.0/23 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.4.0/22 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.8.0/24 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.15.0/24 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.23.0/24 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.26.0/24 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.62.0/24 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.76.0/22 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.120.0/21 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.142.0/23 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.144.0/22 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.160.0/21 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.168.0/23 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.170.0/23 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.180.0/22 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.220.0/23 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.116.222.0/23 | Valid | Nonecovered by 131.116.0.0/16 | 673 100% |
| 131.115.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 131.116.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 192.150.84.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS1729 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 29 are in fix.csv.
- ROA: none3
- Route object: none26
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.43.165.0/24 | No ROA covers it. Add a ROA for AS1729, maxLength 24. |
| ROA: none | 192.43.169.0/24 | No ROA covers it. Add a ROA for AS1729, maxLength 24. |
| ROA: none | 192.121.19.0/24 | No ROA covers it. Add a ROA for AS1729, maxLength 24. |
| Route object: none | 131.115.30.0/23 | No route object for it. A route object for 131.115.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.115.51.0/24 | No route object for it. A route object for 131.115.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.115.80.0/21 | No route object for it. A route object for 131.115.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.115.128.0/20 | No route object for it. A route object for 131.115.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.115.164.0/23 | No route object for it. A route object for 131.115.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.115.192.0/21 | No route object for it. A route object for 131.115.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.115.200.0/22 | No route object for it. A route object for 131.115.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.115.248.0/21 | No route object for it. A route object for 131.115.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.1.0/24 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.2.0/23 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.4.0/22 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.8.0/24 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.15.0/24 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.23.0/24 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.26.0/24 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.62.0/24 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.76.0/22 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.120.0/21 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.142.0/23 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.144.0/22 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.160.0/21 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.168.0/23 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.170.0/23 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.180.0/22 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.220.0/23 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
| Route object: none | 131.116.222.0/23 | No route object for it. A route object for 131.116.0.0/16 with origin AS1729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1729 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS1729 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.