Network · data from 2026-11-12
AS135203 EXCELL-AS - Excell Media Pvt Ltd
Registry name: EXCELL-AS - Excell Media Pvt Ltd, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135203, 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.
| 175.101.255.0/24 | Valid | Other origin onlycovered by 175.101.240.0/20 | 673 100% |
| 175.101.251.0/24 | Valid | Other origin onlycovered by 175.101.240.0/20 | 672 100% |
| 175.101.252.0/24 | Valid | Other origin onlycovered by 175.101.240.0/20 | 672 100% |
| 175.101.253.0/24 | Valid | Other origin onlycovered by 175.101.240.0/20 | 43 6%low visibility |
| 175.101.254.0/24 | Valid | Other origin onlycovered by 175.101.240.0/20 | 43 6%low visibility |
| 175.101.240.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 175.101.241.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 175.101.242.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS135203 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.
- Route object: none5
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 175.101.255.0/24 | Route objects for it name AS17754. A route object for 175.101.240.0/20 with origin AS135203 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135203 in the RIR database for the space. |
| Route object: none | 175.101.251.0/24 | Route objects for it name AS17754. A route object for 175.101.240.0/20 with origin AS135203 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135203 in the RIR database for the space. |
| Route object: none | 175.101.252.0/24 | Route objects for it name AS17754. A route object for 175.101.240.0/20 with origin AS135203 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135203 in the RIR database for the space. |
| Route object: none | 175.101.253.0/24 | Route objects for it name AS17754. A route object for 175.101.240.0/20 with origin AS135203 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135203 in the RIR database for the space. |
| Route object: none | 175.101.254.0/24 | Route objects for it name AS17754. A route object for 175.101.240.0/20 with origin AS135203 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135203 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS135203 whose prefix no peer sees AS135203 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 175.101.240.0/20 | APNIC | Valid |
| 175.101.240.0/21 | APNIC | Valid |
| 175.101.243.0/24 | APNIC | Valid |
| 175.101.244.0/24 | APNIC | Valid |
| 175.101.245.0/24 | APNIC | Valid |
| 175.101.246.0/24 | APNIC | Valid |
| 175.101.247.0/24 | APNIC | 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.