Network · data from 2026-11-12
AS49460 filleck Filleck s.r.o.
Registry name: filleck Filleck s.r.o., SK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49460, 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.
| 185.160.108.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.160.109.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 185.160.110.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 185.160.111.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 2a05:2e00::/32 | No ROA | RIR databaseRIPE | 634 100% |
AS-SET
AS49460 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 5 are in fix.csv.
- ROA: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.160.108.0/24 | No ROA covers it. Add a ROA for AS49460, maxLength 24. |
| ROA: none | 185.160.109.0/24 | No ROA covers it. Add a ROA for AS49460, maxLength 24. |
| ROA: none | 185.160.110.0/24 | No ROA covers it. Add a ROA for AS49460, maxLength 24. |
| ROA: none | 185.160.111.0/24 | No ROA covers it. Add a ROA for AS49460, maxLength 24. |
| ROA: none | 2a05:2e00::/32 | No ROA covers it. Add a ROA for AS49460, maxLength 32. |
Route objects not announced
Every route object with origin AS49460 is announced.
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.