Network · data from 2026-11-12
AS48830 TEC-AS TransEuroCom LLC
Registry name: TEC-AS TransEuroCom LLC, AZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48830, 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.36.200.0/24 | No ROA | Nonecovered by 185.36.200.0/22 | 673 100% |
| 185.36.201.0/24 | No ROA | Nonecovered by 185.36.200.0/22 | 673 100% |
| 185.36.202.0/24 | No ROA | Nonecovered by 185.36.200.0/22 | 673 100% |
| 185.36.203.0/24 | No ROA | Nonecovered by 185.36.200.0/22 | 673 100% |
| 93.88.95.0/24 | No ROA | Nonecovered by 93.88.80.0/20 | 1 0%low visibility |
| 93.88.80.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 31.171.42.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.171.43.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.132.14.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.132.19.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.132.104.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.132.105.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.20.26.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.20.27.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.20.28.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.20.31.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.20.32.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.20.69.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.20.70.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS48830 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 12 are in fix.csv.
- ROA: none6
- Route object: none5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.36.200.0/24 | No ROA covers it. Add a ROA for AS48830, maxLength 24. |
| Route object: none | 185.36.200.0/24 | No route object for it. A route object for 185.36.200.0/22 with origin AS48830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48830 in the RIR database for the space. |
| ROA: none | 185.36.201.0/24 | No ROA covers it. Add a ROA for AS48830, maxLength 24. |
| Route object: none | 185.36.201.0/24 | No route object for it. A route object for 185.36.200.0/22 with origin AS48830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48830 in the RIR database for the space. |
| ROA: none | 185.36.202.0/24 | No ROA covers it. Add a ROA for AS48830, maxLength 24. |
| Route object: none | 185.36.202.0/24 | No route object for it. A route object for 185.36.200.0/22 with origin AS48830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48830 in the RIR database for the space. |
| ROA: none | 185.36.203.0/24 | No ROA covers it. Add a ROA for AS48830, maxLength 24. |
| Route object: none | 185.36.203.0/24 | No route object for it. A route object for 185.36.200.0/22 with origin AS48830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48830 in the RIR database for the space. |
| ROA: none | 93.88.95.0/24 | No ROA covers it. Add a ROA for AS48830, maxLength 24. |
| Route object: none | 93.88.95.0/24 | No route object for it. A route object for 93.88.80.0/20 with origin AS48830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48830 in the RIR database for the space. |
| ROA: none | 93.88.80.0/20 | No ROA covers it. Add a ROA for AS48830, maxLength 20. |
Route objects not announced
Route objects with origin AS48830 whose prefix no peer sees AS48830 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.36.200.0/22 | 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.