Network · data from 2026-11-12
AS57816 SAMEN Samen Ertebat Asr Co. (P.J.S.)
Registry name: SAMEN Samen Ertebat Asr Co. (P.J.S.), IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57816, 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.
| 37.9.248.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 185.118.136.0/22 | No ROA | RIR databaseRIPE | 672 100% |
AS-SET
AS57816 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: none2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 37.9.248.0/22 | No ROA covers it. Add a ROA for AS57816, maxLength 22. |
| ROA: none | 185.118.136.0/22 | No ROA covers it. Add a ROA for AS57816, maxLength 22. |
Route objects not announced
Route objects with origin AS57816 whose prefix no peer sees AS57816 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.9.248.0/23 | RIPE | No ROA |
| 37.9.250.0/23 | RIPE | No ROA |
| 185.118.136.0/23 | RIPE | No ROA |
| 185.118.138.0/23 | 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.