Network · data from 2026-11-12
AS197882 TarinNet
Registry name: Tarin Tarin General Trading and Setting Up Internet Device LTD, IQ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS197882, 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.25.136.0/22 | Valid | Nonecovered by 31.25.136.0/21 | 673 100% |
| 185.254.84.0/24 | Valid | None | 673 100% |
| 31.25.136.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.25.137.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.25.138.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.25.139.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.25.140.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.25.141.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.25.142.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 130.255.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 130.255.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 130.255.94.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 130.255.95.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 159.255.160.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 159.255.161.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 159.255.162.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 159.255.163.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 159.255.164.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 159.255.165.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 159.255.166.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.14.248.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.14.250.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.14.251.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.75.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.101.236.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.101.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.101.238.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.101.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.184.198.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.184.199.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.212.33.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.47.189.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 130.255.88.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 130.255.89.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 130.255.90.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 130.255.91.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a03:bcc0:1::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS197882's PeeringDB record names no 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 19 are in fix.csv.
- Route object: none2
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 31.25.136.0/22 | No route object for it. A route object for 31.25.136.0/21 with origin AS197882 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197882 in the RIR database for the space. |
| Route object: none | 185.254.84.0/24 | No route object for it. Add a route object with origin AS197882 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS197882 whose prefix no peer sees AS197882 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.25.136.0/21 | RIPE | No ROA |
| 31.25.140.0/23 | RIPE | No ROA |
| 31.25.142.0/24 | RIPE | Valid |
| 31.25.143.0/24 | RIPE | Valid |
| 130.255.88.0/22 | RIPE | No ROA |
| 130.255.92.0/22 | RIPE | No ROA |
| 159.255.160.0/21 | RIPE | No ROA |
| 159.255.160.0/22 | RIPE | Valid |
| 159.255.166.0/24 | RIPE | Valid |
| 159.255.167.0/24 | RIPE | Valid |
| 185.14.248.0/22 | RIPE | No ROA |
| 185.14.248.0/24 | RIPE | Invalid: maxLength |
| 185.14.249.0/24 | RIPE | Invalid: maxLength |
| 185.14.250.0/23 | RIPE | No ROA |
| 185.101.236.0/22 | RIPE | No ROA |
| 185.184.196.0/22 | RIPE | No ROA |
| 185.184.197.0/24 | RIPE | Invalid: origin |
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.