Network · data from 2026-11-12
AS28889 LinzNet ISP GmbH
Registry name: LINZNET-AS LinzNet Internet Service Provider GmbH, AT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28889, 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.
| 91.206.236.0/23 | No ROA | None | 673 100% |
| 185.249.124.0/22 | No ROA | Other origin only | 0 0%low visibility |
| 185.135.18.0/24 | Valid | Other origin only | 338 50% |
| 185.135.19.0/24 | Valid | Other origin only | 338 50% |
| 80.66.32.0/19 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 85.193.128.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 85.193.176.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 91.206.236.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.206.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.54.208.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.54.209.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.46.100.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.187.252.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.187.254.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.46.101.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.46.102.0/23 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS28889: AS-LINZNET. 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 (AS28889 isn't in the set, or no route object for AS28889 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 | AS28889 in it | Not covered |
|---|---|---|---|---|---|
| AS-LINZNET | RIPE | 21 | 7 | 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 13 are in fix.csv.
- ROA: none2
- Route object: none4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.206.236.0/23 | No ROA covers it. Add a ROA for AS28889, maxLength 23. |
| Route object: none | 91.206.236.0/23 | No route object for it. Add a route object with origin AS28889 in the RIR database for the space. |
| ROA: none | 185.249.124.0/22 | No ROA covers it. Add a ROA for AS28889, maxLength 22. |
| Route object: none | 185.249.124.0/22 | Route objects for it name AS204419. Add a route object with origin AS28889 in the RIR database for the space. |
| Route object: none | 185.135.18.0/24 | Route objects for it name AS43848, AS208350. Add a route object with origin AS28889 in the RIR database for the space. |
| Route object: none | 185.135.19.0/24 | Route objects for it name AS43848, AS208350. Add a route object with origin AS28889 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28889 whose prefix no peer sees AS28889 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.233.7.0/24 | RIPE | No ROA |
| 91.233.12.0/23 | RIPE | No ROA |
| 185.135.16.0/24 | RIPE | Valid |
| 185.135.17.0/24 | RIPE | Valid |
| 185.148.236.0/22 | RIPE | No ROA |
| 193.187.247.0/24 | RIPE | No ROA |
| 2a00:eb40::/32 | RIPE | Valid |
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.