Network · data from 2026-11-12
AS24744 SiNET-SK-AS SiNET Telecom s.r.o.
Registry name: SiNET-SK-AS SiNET Telecom s.r.o., SK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24744, 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.169.160.0/23 | No ROA | Nonecovered by 62.169.160.0/20 | 671 100% |
| 62.169.162.0/23 | No ROA | Nonecovered by 62.169.160.0/20 | 671 100% |
| 62.169.164.0/22 | No ROA | Nonecovered by 62.169.160.0/20 | 671 100% |
| 62.169.168.0/21 | No ROA | Nonecovered by 62.169.160.0/20 | 671 100% |
| 62.169.182.0/24 | No ROA | Nonecovered by 62.169.182.0/23 | 671 100% |
| 62.169.183.0/24 | No ROA | Nonecovered by 62.169.182.0/23 | 671 100% |
AS-SET
AS24744 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 14 are in fix.csv.
- ROA: none6
- Route object: none6
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 62.169.160.0/23 | No ROA covers it. Add a ROA for AS24744, maxLength 23. |
| Route object: none | 62.169.160.0/23 | No route object for it. A route object for 62.169.160.0/20 with origin AS24744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24744 in the RIR database for the space. |
| ROA: none | 62.169.162.0/23 | No ROA covers it. Add a ROA for AS24744, maxLength 23. |
| Route object: none | 62.169.162.0/23 | No route object for it. A route object for 62.169.160.0/20 with origin AS24744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24744 in the RIR database for the space. |
| ROA: none | 62.169.164.0/22 | No ROA covers it. Add a ROA for AS24744, maxLength 22. |
| Route object: none | 62.169.164.0/22 | No route object for it. A route object for 62.169.160.0/20 with origin AS24744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24744 in the RIR database for the space. |
| ROA: none | 62.169.168.0/21 | No ROA covers it. Add a ROA for AS24744, maxLength 21. |
| Route object: none | 62.169.168.0/21 | No route object for it. A route object for 62.169.160.0/20 with origin AS24744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24744 in the RIR database for the space. |
| ROA: none | 62.169.182.0/24 | No ROA covers it. Add a ROA for AS24744, maxLength 24. |
| Route object: none | 62.169.182.0/24 | No route object for it. A route object for 62.169.182.0/23 with origin AS24744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24744 in the RIR database for the space. |
| ROA: none | 62.169.183.0/24 | No ROA covers it. Add a ROA for AS24744, maxLength 24. |
| Route object: none | 62.169.183.0/24 | No route object for it. A route object for 62.169.182.0/23 with origin AS24744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24744 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24744 whose prefix no peer sees AS24744 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 62.169.160.0/20 | RIPE | No ROA |
| 62.169.182.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.