Network · data from 2026-11-12
AS39074 Sepanta Communication Development Co. Ltd
Registry name: IR-SEPANTA Sepanta Communication Development Co. Ltd, IR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39074, 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.
| 85.133.166.0/24 | Valid | Other origin only | 671 100% |
| 85.133.174.0/24 | Valid | None | 671 100% |
| 85.133.251.0/24 | Valid | None | 670 100% |
| 85.133.128.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.129.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.130.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.131.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.132.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.133.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.135.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.136.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.137.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.138.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.139.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.141.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.143.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.145.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.146.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.147.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.148.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.149.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.150.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.154.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.155.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.156.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.157.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.158.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.159.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.164.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.165.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.167.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.168.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.171.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.172.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.173.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.175.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.176.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.177.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.178.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.179.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.180.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.181.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.182.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.183.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.184.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.185.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.186.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.187.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.188.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.189.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.190.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.191.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.192.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.209.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.210.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.211.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.212.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.213.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.218.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.222.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.231.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.232.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.235.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.255.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.133.142.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 85.133.223.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 85.133.252.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 2a04:87c1::/32 | Valid | RIR databaseRIPE | 635 100% |
| 85.133.134.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 85.133.152.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS39074'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 37 are in fix.csv.
- Route object: none3
- Route object: not announced34
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 85.133.166.0/24 | Route objects for it name AS204104. Add a route object with origin AS39074 in the RIR database for the space. |
| Route object: none | 85.133.174.0/24 | No route object for it. Add a route object with origin AS39074 in the RIR database for the space. |
| Route object: none | 85.133.251.0/24 | No route object for it. Add a route object with origin AS39074 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS39074 whose prefix no peer sees AS39074 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.160.206.0/23 | RIPE | Invalid: origin |
| 5.160.206.0/24 | RIPE | Invalid: origin |
| 5.160.207.0/24 | RIPE | Invalid: origin |
| 5.202.136.0/22 | RIPE | Valid |
| 5.202.136.0/23 | RIPE | Valid |
| 5.202.136.0/24 | RIPE | Valid |
| 5.202.137.0/24 | RIPE | Valid |
| 5.202.138.0/23 | RIPE | Valid |
| 5.202.138.0/24 | RIPE | Valid |
| 5.202.139.0/24 | RIPE | Valid |
| 85.133.128.0/22 | RIPE | Valid |
| 85.133.128.0/23 | RIPE | Invalid: maxLength |
| 85.133.144.0/23 | RIPE | No ROA |
| 85.133.144.0/24 | RIPE | Valid |
| 85.133.148.0/23 | RIPE | No ROA |
| 85.133.154.0/23 | RIPE | No ROA |
| 85.133.158.0/23 | RIPE | No ROA |
| 85.133.168.0/22 | RIPE | Valid |
| 85.133.168.0/23 | RIPE | Valid |
| 85.133.170.0/23 | RIPE | Valid |
| 85.133.172.0/23 | RIPE | Valid |
| 85.133.176.0/23 | RIPE | Valid |
| 85.133.180.0/22 | RIPE | Valid |
| 85.133.180.0/23 | RIPE | Valid |
| 85.133.184.0/22 | RIPE | Valid |
| 85.133.188.0/22 | RIPE | Valid |
| 85.133.190.0/23 | RIPE | Invalid: maxLength |
| 85.133.199.0/24 | RIPE | Invalid: origin |
| 85.133.203.0/24 | RIPE | Invalid: origin |
| 85.133.206.0/23 | RIPE | No ROA |
| 85.133.210.0/23 | RIPE | Valid |
| 85.133.212.0/23 | RIPE | No ROA |
| 85.133.214.0/24 | RIPE | Invalid: origin |
| 85.133.219.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.