Network · data from 2026-11-12
AS57722 ATI-KOS-AS N.SH.T "ATI-KOS" sh.p.k
Registry name: ATI-KOS-AS N.SH.T "ATI-KOS" sh.p.k, RS · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57722, 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.
| 2a07:b200::/31 | No ROA | None | 237 37% |
| 185.248.172.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.248.173.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.248.174.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.248.175.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS57722 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 3 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a07:b200::/31 | No ROA covers it. Add a ROA for AS57722, maxLength 31. |
| Route object: none | 2a07:b200::/31 | No route object for it. Add a route object with origin AS57722 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS57722 whose prefix no peer sees AS57722 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.248.172.0/22 | RIPE | Valid |
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.