Network · data from 2026-11-12
AS205288 Tekanet FIRMA PRZEMYSLOWO-HANDLOWO-USLUGOWA "TEKANET" KONRAD NIEWIEDZIAL
Registry name: Tekanet FIRMA PRZEMYSLOWO-HANDLOWO-USLUGOWA "TEKANET" KONRAD NIEWIEDZIAL, PL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205288, 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.
| 195.20.138.195/32 | No ROA | Nonecovered by 195.20.138.0/24 | 2 0%low visibility |
| 195.20.138.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS205288 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 4 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 195.20.138.195/32 | No ROA covers it. Add a ROA for AS205288, maxLength 32. |
| Route object: none | 195.20.138.195/32 | No route object for it. A route object for 195.20.138.0/24 with origin AS205288 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS205288 in the RIR database for the space. |
| ROA: none | 195.20.138.0/24 | No ROA covers it. Add a ROA for AS205288, maxLength 24. |
Route objects not announced
Route objects with origin AS205288 whose prefix no peer sees AS205288 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a10:f781:10:99b5::/64 | 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.