Network · data from 2026-11-12
AS139195 Seans Media Pvt Ltd
Registry name: SEANSMEDIAPVTLTD-AS-AP - Seans Media Pvt Ltd, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139195, 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.
| 38.175.36.0/24 | Invalid: origin | Other origin only | 4 1%low visibility |
| 38.183.105.0/24 | Invalid: origin | Other origin only | 4 1%low visibility |
| 103.130.108.0/24 | Invalid: origin | Other origin only | 4 1%low visibility |
| 193.32.246.0/24 | Invalid: origin | Other origin only | 4 1%low visibility |
| 103.42.74.0/24 | Invalid: maxLength | Other origin onlycovered by 103.42.74.0/23 | 4 1%low visibility |
| 103.42.73.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.42.75.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.139.156.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.139.157.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.139.158.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.139.159.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.174.70.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.174.71.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 119.161.96.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 119.161.97.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 119.161.98.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 119.161.99.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df6:4900::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2404:e740:1::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2404:e740:2::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2404:e740:3::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2404:e740::/32 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:e740::/48 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS139195: AS139195:AS-SEANS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS139195 isn't in the set, or no route object for AS139195 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS139195 in it | Not covered |
|---|---|---|---|---|---|
| AS139195:AS-SEANS | APNIClists itself further down | 137 | 11 | Yes | 4 |
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 19 are in fix.csv.
- ROA: origin4
- ROA: maxLength1
- Route object: none5
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 38.175.36.0/24 | ROAs covering it name AS147185, not AS139195. If AS139195 should announce it, add a ROA for AS139195. |
| Route object: none | 38.175.36.0/24 | Route objects for it name AS147185. Add a route object with origin AS139195 in the RIR database for the space. |
| ROA: origin | 38.183.105.0/24 | ROAs covering it name AS147185, not AS139195. If AS139195 should announce it, add a ROA for AS139195. |
| Route object: none | 38.183.105.0/24 | Route objects for it name AS147185. Add a route object with origin AS139195 in the RIR database for the space. |
| ROA: origin | 103.130.108.0/24 | ROAs covering it name AS147185, not AS139195. If AS139195 should announce it, add a ROA for AS139195. |
| Route object: none | 103.130.108.0/24 | Route objects for it name AS147185. Add a route object with origin AS139195 in the RIR database for the space. |
| ROA: origin | 193.32.246.0/24 | ROAs covering it name AS147185, not AS139195. If AS139195 should announce it, add a ROA for AS139195. |
| Route object: none | 193.32.246.0/24 | Route objects for it name AS147185. Add a route object with origin AS139195 in the RIR database for the space. |
| ROA: maxLength | 103.42.74.0/24 | ROA 103.42.72.0/22 AS139195 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 103.42.74.0/24. |
| Route object: none | 103.42.74.0/24 | Route objects for it name AS133664, AS147185. A route object for 103.42.74.0/23 with origin AS139195 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139195 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS139195 whose prefix no peer sees AS139195 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.42.72.0/22 | APNIC | Valid |
| 103.42.72.0/23 | APNIC | Valid |
| 103.42.74.0/23 | APNIC | Valid |
| 103.171.58.0/23 | APNIC | Valid |
| 103.171.58.0/24 | APNIC | Valid |
| 103.171.59.0/24 | APNIC | Valid |
| 119.161.96.0/22 | APNIC | Valid |
| 119.161.96.0/23 | APNIC | Valid |
| 119.161.98.0/23 | 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.