Network · data from 2026-11-12
AS202204 Teneo TENEO DIGITAL AS
Registry name: Teneo TENEO DIGITAL AS, NO · not in PeeringDB
31IPv4 routes
100.0% RPKI valid · 64.5% with a route object
5IPv6 routes
80.0% RPKI valid · 40.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
14 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
27Route objects not announced
registered with origin AS202204, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS202204, 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.
| 2a09:5c0::/29 | No ROA | None | 2 0%low visibility |
| 2a00:ea0:1000::/48 | Valid | Nonecovered by 2a00:ea0::/32 | 349 55% |
| 2a00:ea0:1001::/48 | Valid | Nonecovered by 2a00:ea0::/32 | 349 55% |
| 109.72.168.0/21 | Valid | Nonecovered by 109.72.160.0/20 | 148 22% |
| 78.26.20.0/23 | Valid | Nonecovered by 78.26.20.0/22 | 146 22% |
| 78.26.32.0/22 | Valid | Nonecovered by 78.26.32.0/21 | 146 22% |
| 78.26.36.0/22 | Valid | Nonecovered by 78.26.32.0/21 | 146 22% |
| 78.26.48.0/23 | Valid | Nonecovered by 78.26.48.0/22 | 146 22% |
| 78.26.50.0/23 | Valid | Nonecovered by 78.26.48.0/22 | 146 22% |
| 78.26.56.0/23 | Valid | Nonecovered by 78.26.56.0/21 | 146 22% |
| 78.26.60.0/22 | Valid | Nonecovered by 78.26.56.0/21 | 146 22% |
| 109.72.164.0/22 | Valid | Nonecovered by 109.72.160.0/20 | 146 22% |
| 141.195.24.0/22 | Valid | Nonecovered by 141.195.16.0/20 | 146 22% |
| 85.113.76.0/22 | Valid | Nonecovered by 85.113.72.0/21 | 145 22% |
| 2.58.24.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 78.26.0.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 78.26.0.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 78.26.32.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 85.113.72.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 109.72.160.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 139.28.124.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 141.195.16.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 152.228.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 152.228.64.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 152.228.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 171.22.152.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.100.204.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.124.54.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.161.136.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 2.58.26.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 2a00:ea0::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a00:ea0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 78.26.32.0/21 | Valid | RIR databaseRIPE | 148 22% |
| 78.26.40.0/21 | Valid | RIR databaseRIPE | 148 22% |
| 78.26.16.0/23 | Valid | RIR databaseRIPE | 146 22% |
| 78.26.24.0/23 | Valid | RIR databaseRIPE | 146 22% |
AS-SET
AS202204 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 42 are in fix.csv.
- ROA: none1
- Route object: none14
- Route object: not announced27
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a09:5c0::/29 | No ROA covers it. Add a ROA for AS202204, maxLength 29. |
| Route object: none | 2a09:5c0::/29 | No route object for it. Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 2a00:ea0:1000::/48 | No route object for it. A route object for 2a00:ea0::/32 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 2a00:ea0:1001::/48 | No route object for it. A route object for 2a00:ea0::/32 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 109.72.168.0/21 | No route object for it. A route object for 109.72.160.0/20 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 78.26.20.0/23 | No route object for it. A route object for 78.26.20.0/22 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 78.26.32.0/22 | No route object for it. A route object for 78.26.32.0/21 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 78.26.36.0/22 | No route object for it. A route object for 78.26.32.0/21 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 78.26.48.0/23 | No route object for it. A route object for 78.26.48.0/22 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 78.26.50.0/23 | No route object for it. A route object for 78.26.48.0/22 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 78.26.56.0/23 | No route object for it. A route object for 78.26.56.0/21 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 78.26.60.0/22 | No route object for it. A route object for 78.26.56.0/21 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 109.72.164.0/22 | No route object for it. A route object for 109.72.160.0/20 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 141.195.24.0/22 | No route object for it. A route object for 141.195.16.0/20 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
| Route object: none | 85.113.76.0/22 | No route object for it. A route object for 85.113.72.0/21 with origin AS202204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202204 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202204 whose prefix no peer sees AS202204 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2.58.27.0/24 | RIPE | Valid |
| 78.26.0.0/24 | RIPE | Invalid: maxLength |
| 78.26.1.0/24 | RIPE | Invalid: maxLength |
| 78.26.2.0/24 | RIPE | Invalid: maxLength |
| 78.26.3.0/24 | RIPE | Invalid: maxLength |
| 78.26.4.0/22 | RIPE | Valid |
| 78.26.8.0/21 | RIPE | Valid |
| 78.26.18.0/23 | RIPE | Valid |
| 78.26.20.0/22 | RIPE | Valid |
| 78.26.26.0/24 | RIPE | Invalid: maxLength |
| 78.26.27.0/24 | RIPE | Invalid: maxLength |
| 78.26.28.0/22 | RIPE | Valid |
| 78.26.48.0/22 | RIPE | Valid |
| 78.26.52.0/24 | RIPE | Invalid: maxLength |
| 78.26.53.0/24 | RIPE | Invalid: maxLength |
| 78.26.54.0/23 | RIPE | Valid |
| 78.26.56.0/21 | RIPE | Valid |
| 141.195.8.0/21 | RIPE | Valid |
| 176.124.60.0/22 | RIPE | Valid |
| 176.125.244.0/22 | RIPE | Valid |
| 185.97.196.0/22 | RIPE | Valid |
| 185.135.134.0/23 | RIPE | Invalid: origin |
| 185.154.16.0/22 | RIPE | Invalid: origin |
| 185.180.232.0/22 | RIPE | Valid |
| 185.181.80.0/22 | RIPE | Valid |
| 2a00:ea0::/30 | RIPE | Valid |
| 2a06:700::/29 | RIPE | 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.