Network · data from 2026-11-12
AS36068 APPDIRECT - AppDirect
Registry name: APPDIRECT - AppDirect, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36068, 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.
| 173.241.45.0/24 | Valid | Other origin onlycovered by 173.241.44.0/23 | 673 100% |
| 173.241.41.0/24 | Valid | Other origin onlycovered by 173.241.40.0/23 | 14 2%low visibility |
| 173.241.40.0/24 | Valid | Other origin onlycovered by 173.241.40.0/23 | 3 0%low visibility |
| 173.241.32.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 173.241.43.0/24 | Valid | RIR databaseARIN | 673 100% |
| 173.241.33.0/24 | Valid | RIR databaseARIN | 671 100% |
| 173.241.34.0/24 | Valid | RIR databaseARIN | 671 100% |
| 173.241.35.0/24 | Valid | RIR databaseARIN | 671 100% |
| 173.241.36.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS36068 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 14 are in fix.csv.
- Route object: none3
- Route object: RIR1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 173.241.45.0/24 | Route objects for it name AS603. A route object for 173.241.44.0/23 with origin AS36068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36068 in the RIR database for the space. |
| Route object: none | 173.241.41.0/24 | Route objects for it name AS603. A route object for 173.241.40.0/23 with origin AS36068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36068 in the RIR database for the space. |
| Route object: none | 173.241.40.0/24 | Route objects for it name AS603. A route object for 173.241.40.0/23 with origin AS36068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36068 in the RIR database for the space. |
| Route object: RIR | 173.241.32.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36068 whose prefix no peer sees AS36068 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 173.241.32.0/20 | ALTDB, ARIN, RADB | Valid |
| 173.241.32.0/21 | ARIN | Valid |
| 173.241.32.0/23 | ARIN | Valid |
| 173.241.37.0/24 | ARIN | Valid |
| 173.241.38.0/24 | ARIN | Valid |
| 173.241.39.0/24 | ARIN | Valid |
| 173.241.40.0/23 | ARIN | Valid |
| 173.241.42.0/24 | ARIN | Valid |
| 173.241.44.0/23 | ARIN | Valid |
| 173.241.45.0/29 | ARIN | Invalid: maxLength |
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.