Network · data from 2026-11-12
AS208145 Krzysztof Frac
Registry name: TEL-NET-AS Krzysztof Frac trading as "TEL-NET", PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208145, 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.227.190.10/32 | Invalid: maxLength | Nonecovered by 185.227.190.0/24 | 2 0%low visibility |
| 185.227.190.21/32 | Invalid: maxLength | Nonecovered by 185.227.190.0/24 | 2 0%low visibility |
| 185.227.190.91/32 | Invalid: maxLength | Nonecovered by 185.227.190.0/24 | 2 0%low visibility |
| 185.227.190.92/32 | Invalid: maxLength | Nonecovered by 185.227.190.0/24 | 2 0%low visibility |
| 185.227.190.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS208145: RIPE::AS-TEL-NET-PL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS208145 isn't in the set, or no route object for AS208145 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS208145 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-TEL-NET-PL | RIPE | 2 | 1 | Yes | 4 |
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 9 are in fix.csv.
- ROA: maxLength4
- Route object: none4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 185.227.190.10/32 | ROA 185.227.190.0/24 AS208145 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.227.190.10/32. |
| Route object: none | 185.227.190.10/32 | No route object for it. A route object for 185.227.190.0/24 with origin AS208145 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS208145 in the RIR database for the space. |
| ROA: maxLength | 185.227.190.21/32 | ROA 185.227.190.0/24 AS208145 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.227.190.21/32. |
| Route object: none | 185.227.190.21/32 | No route object for it. A route object for 185.227.190.0/24 with origin AS208145 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS208145 in the RIR database for the space. |
| ROA: maxLength | 185.227.190.91/32 | ROA 185.227.190.0/24 AS208145 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.227.190.91/32. |
| Route object: none | 185.227.190.91/32 | No route object for it. A route object for 185.227.190.0/24 with origin AS208145 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS208145 in the RIR database for the space. |
| ROA: maxLength | 185.227.190.92/32 | ROA 185.227.190.0/24 AS208145 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.227.190.92/32. |
| Route object: none | 185.227.190.92/32 | No route object for it. A route object for 185.227.190.0/24 with origin AS208145 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS208145 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS208145 whose prefix no peer sees AS208145 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a10:f781:10:8fbf::/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.