Network · data from 2026-11-12
AS208560 Sepehrnet SEPEHR NET IRANIAN PJSC
Registry name: Sepehrnet SEPEHR NET IRANIAN PJSC, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208560, 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.
| 2a10:fe00::/32 | No ROA | RIR databaseRIPE | 633 100% |
| 83.150.192.0/23 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS208560 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 6 are in fix.csv.
- ROA: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a10:fe00::/32 | No ROA covers it. Add a ROA for AS208560, maxLength 32. |
Route objects not announced
Route objects with origin AS208560 whose prefix no peer sees AS208560 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 83.150.192.0/22 | RIPE | No ROA |
| 83.150.192.0/24 | RIPE | Valid |
| 83.150.193.0/24 | RIPE | Valid |
| 2a10:fe00::/33 | RIPE | No ROA |
| 2a10:fe00:8000::/33 | 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.