Network · data from 2026-11-12
AS401190 TREE-AS401190 - TREE TELECOM
Registry name: TREE-AS401190 - TREE TELECOM, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS401190, 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.
| 31.57.212.0/23 | Invalid: origin | Other origin only | 2 0%low visibility |
| 2602:f894::/44 | Valid | Nonecovered by 2602:f894::/36 | 635 100% |
| 2602:f894:10::/44 | Valid | Nonecovered by 2602:f894::/36 | 635 100% |
| 2602:f894:20::/44 | Valid | Nonecovered by 2602:f894::/36 | 635 100% |
| 2602:f894:30::/44 | Valid | Nonecovered by 2602:f894::/36 | 635 100% |
| 2602:f894:40::/44 | Valid | Nonecovered by 2602:f894::/36 | 635 100% |
| 2602:f894:50::/44 | Valid | Nonecovered by 2602:f894::/36 | 635 100% |
| 147.78.120.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 147.79.7.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 150.241.138.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
AS-SET
AS401190 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: origin1
- Route object: none7
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 31.57.212.0/23 | ROAs covering it name AS834, not AS401190. If AS401190 should announce it, add a ROA for AS401190. |
| Route object: none | 31.57.212.0/23 | Route objects for it name AS834. Add a route object with origin AS401190 in the RIR database for the space. |
| Route object: none | 2602:f894::/44 | No route object for it. A route object for 2602:f894::/36 with origin AS401190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401190 in the RIR database for the space. |
| Route object: none | 2602:f894:10::/44 | No route object for it. A route object for 2602:f894::/36 with origin AS401190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401190 in the RIR database for the space. |
| Route object: none | 2602:f894:20::/44 | No route object for it. A route object for 2602:f894::/36 with origin AS401190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401190 in the RIR database for the space. |
| Route object: none | 2602:f894:30::/44 | No route object for it. A route object for 2602:f894::/36 with origin AS401190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401190 in the RIR database for the space. |
| Route object: none | 2602:f894:40::/44 | No route object for it. A route object for 2602:f894::/36 with origin AS401190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401190 in the RIR database for the space. |
| Route object: none | 2602:f894:50::/44 | No route object for it. A route object for 2602:f894::/36 with origin AS401190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401190 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS401190 whose prefix no peer sees AS401190 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.65.114.0/24 | RADB, RIPE | Valid |
| 45.65.115.0/24 | RADB, RIPE | Valid |
| 150.241.216.0/21 | RADB, RIPE | Valid |
| 2602:f894::/36 | 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.