Network · data from 2026-11-12
AS41828 TELEMACH-HOSTING Telemach Slovenija d.o.o.
Registry name: TELEMACH-HOSTING Telemach Slovenija d.o.o., SI · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41828, 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.
| 2a01:b4a0:1000::/48 | No ROA | RIR databaseRIPE | 633 100% |
| 185.53.12.0/23 | Valid | None | 671 100% |
| 91.185.192.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 185.53.12.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.47.228.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.191.96.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a02:840::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS41828 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 2 are in fix.csv.
- ROA: none1
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a01:b4a0:1000::/48 | No ROA covers it. Add a ROA for AS41828, maxLength 48. |
| Route object: none | 185.53.12.0/23 | No route object for it. Add a route object with origin AS41828 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS41828 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.