Network · data from 2026-11-12
AS44375 Asmanfaraz Sepahan Company (P.J.S)
Registry name: AISDP Asmanfaraz Sepahan Company (P.J.S), IR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44375, 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.
| 91.230.32.0/24 | No ROA | None | 665 99% |
| 93.126.0.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 193.178.200.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 2a13:f140::/29 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS44375: RIPE::AS-ISDP. 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 (AS44375 isn't in the set, or no route object for AS44375 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 | AS44375 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-ISDP | RIPE | 13 | 1 | Yes | 1 |
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 39 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced37
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.230.32.0/24 | No ROA covers it. Add a ROA for AS44375, maxLength 24. |
| Route object: none | 91.230.32.0/24 | No route object for it. Add a route object with origin AS44375 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS44375 whose prefix no peer sees AS44375 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.143.251.0/24 | RIPE | Invalid: origin |
| 93.126.0.0/24 | RIPE | Invalid: maxLength |
| 93.126.6.0/24 | RIPE | Invalid: maxLength |
| 93.126.9.0/24 | RIPE | Valid |
| 93.126.12.0/24 | RIPE | Invalid: maxLength |
| 93.126.14.0/24 | RIPE | Invalid: maxLength |
| 93.126.18.0/24 | RIPE | Invalid: maxLength |
| 93.126.24.0/24 | RIPE | Invalid: maxLength |
| 93.126.27.0/24 | RIPE | Invalid: maxLength |
| 93.126.30.0/24 | RIPE | Invalid: maxLength |
| 93.126.31.0/24 | RIPE | Invalid: maxLength |
| 93.126.32.0/19 | RIPE | Invalid: maxLength |
| 93.126.32.0/24 | RIPE | Invalid: maxLength |
| 93.126.33.0/24 | RIPE | Invalid: maxLength |
| 93.126.34.0/24 | RIPE | Invalid: maxLength |
| 93.126.35.0/24 | RIPE | Invalid: maxLength |
| 93.126.36.0/24 | RIPE | Invalid: maxLength |
| 93.126.37.0/24 | RIPE | Invalid: maxLength |
| 93.126.38.0/24 | RIPE | Invalid: maxLength |
| 93.126.39.0/24 | RIPE | Invalid: maxLength |
| 93.126.40.0/24 | RIPE | Invalid: maxLength |
| 93.126.41.0/24 | RIPE | Invalid: maxLength |
| 93.126.42.0/24 | RIPE | Invalid: maxLength |
| 93.126.43.0/24 | RIPE | Invalid: maxLength |
| 93.126.49.0/24 | RIPE | Invalid: maxLength |
| 93.126.51.0/24 | RIPE | Invalid: maxLength |
| 93.126.54.0/24 | RIPE | Invalid: maxLength |
| 93.126.56.0/24 | RIPE | Invalid: maxLength |
| 93.126.59.0/24 | RIPE | Invalid: maxLength |
| 93.126.60.0/24 | RIPE | Invalid: maxLength |
| 93.126.61.0/24 | RIPE | Invalid: maxLength |
| 93.126.62.0/24 | RIPE | Invalid: maxLength |
| 93.126.63.0/24 | RIPE | Invalid: maxLength |
| 193.178.200.0/24 | RIPE | Valid |
| 193.178.201.0/24 | RIPE | Valid |
| 193.178.202.0/24 | RIPE | Valid |
| 193.178.203.0/24 | RIPE | 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.