Network · data from 2026-11-12
AS44546 ALFATELECOM-AS ALFA TELECOM s.r.o.
Registry name: ALFATELECOM-AS ALFA TELECOM s.r.o., CZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44546, 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.
| 31.148.242.0/24 | Valid | Other origin onlycovered by 31.148.0.0/16 | 137 20% |
| 31.148.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 92.38.0.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 92.253.128.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 93.170.0.0/15 | Valid | RIR databaseRIPE | 673 100% |
| 95.46.0.0/15 | Valid | RIR databaseRIPE | 673 100% |
| 146.120.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 146.158.0.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 151.249.128.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 185.67.252.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.178.4.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 91.201.20.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 93.170.98.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.46.122.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS44546 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 1 are in fix.csv.
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 31.148.242.0/24 | Route objects for it name AS204720. A route object for 31.148.0.0/16 with origin AS44546 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44546 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS44546 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.