Network · data from 2026-11-12
AS5618 DPI DP IRAN PLC
Registry name: DPI DP IRAN PLC, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS5618, 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.
| 62.193.4.0/24 | Valid | Nonecovered by 62.193.4.0/22 | 670 100% |
| 62.193.6.0/24 | Valid | Nonecovered by 62.193.4.0/22 | 670 100% |
| 62.193.8.0/24 | Valid | Nonecovered by 62.193.8.0/21 | 670 100% |
| 62.193.12.0/23 | Valid | Nonecovered by 62.193.8.0/21 | 670 100% |
| 62.193.17.0/24 | Valid | Nonecovered by 62.193.16.0/21 | 670 100% |
| 62.193.3.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.193.13.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.193.5.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.193.7.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.193.16.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 62.193.18.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 62.193.20.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS5618 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 21 are in fix.csv.
- Route object: none5
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 62.193.4.0/24 | No route object for it. A route object for 62.193.4.0/22 with origin AS5618 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5618 in the RIR database for the space. |
| Route object: none | 62.193.6.0/24 | No route object for it. A route object for 62.193.4.0/22 with origin AS5618 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5618 in the RIR database for the space. |
| Route object: none | 62.193.8.0/24 | No route object for it. A route object for 62.193.8.0/21 with origin AS5618 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5618 in the RIR database for the space. |
| Route object: none | 62.193.12.0/23 | No route object for it. A route object for 62.193.8.0/21 with origin AS5618 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5618 in the RIR database for the space. |
| Route object: none | 62.193.17.0/24 | No route object for it. A route object for 62.193.16.0/21 with origin AS5618 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5618 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS5618 whose prefix no peer sees AS5618 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 62.193.0.0/21 | RIPE | No ROA |
| 62.193.0.0/22 | RIPE | No ROA |
| 62.193.2.0/24 | RIPE | No ROA |
| 62.193.4.0/22 | RIPE | No ROA |
| 62.193.8.0/21 | RIPE | No ROA |
| 62.193.9.0/24 | RIPE | No ROA |
| 62.193.10.0/24 | RIPE | No ROA |
| 62.193.11.0/24 | RIPE | No ROA |
| 62.193.12.0/24 | RIPE | Invalid: maxLength |
| 62.193.14.0/24 | RIPE | Valid |
| 62.193.15.0/24 | RIPE | Valid |
| 62.193.16.0/21 | RIPE | No ROA |
| 62.193.19.0/24 | RIPE | No ROA |
| 62.193.21.0/24 | RIPE | Valid |
| 62.193.22.0/24 | RIPE | No ROA |
| 62.193.23.0/24 | RIPE | No ROA |
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.