bgpreport

Network · data from 2026-11-12

AS35369 LINZ AG TELEKOM

Registry name: LINZAG-TELEKOM-AS LINZ STROM GAS WAERME GmbH fuer Energiedienstleistungen und Telekommunikation, AT · PeeringDB

10IPv4 routes 20.0% RPKI valid · 90.0% with a route object
2IPv6 routes 50.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS35369, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS35369, 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.197.181.0/24 No ROA None 673 100% 67
91.198.240.0/24 No ROA RIR databaseRIPE 673 100% 66
185.168.100.0/22 No ROA RIR databaseRIPE 673 100% 66
185.242.177.0/24 No ROA RIR databaseRIPE 673 100% 66
193.104.82.0/24 No ROA RIR databaseRIPE 673 100% 66
193.186.164.0/22 No ROA RIR databaseRIPE 673 100% 66
193.186.168.0/22 No ROA RIR databaseRIPE 673 100% 66
194.116.158.0/23 No ROA RIR databaseRIPE 673 100% 66
2602:810:2081::/48 No ROA RIR databaseARIN 634 100% 70
83.164.128.0/17 Valid RIR databaseRIPE 673 100% 66
185.121.40.0/22 Valid RIR databaseRIPE 673 100% 66
2a00:1860::/32 Valid RIR databaseRIPE 634 100% 70

AS-SET

PeeringDB's irr_as_set for AS35369: RIPE::AS-LAGIS. 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 (AS35369 isn't in the set, or no route object for AS35369 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.

NameDatabaseASNsSets Route objectsAS35369 in itNot covered
RIPE::AS-LAGIS RIPE 17292 Yes 1

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 10 are in fix.csv.

  • ROA: none9
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none185.197.181.0/24No ROA covers it. Add a ROA for AS35369, maxLength 24.673 of 673
Route object: none185.197.181.0/24No route object for it. Add a route object with origin AS35369 in the RIR database for the space.673 of 673
ROA: none91.198.240.0/24No ROA covers it. Add a ROA for AS35369, maxLength 24.673 of 673
ROA: none185.168.100.0/22No ROA covers it. Add a ROA for AS35369, maxLength 22.673 of 673
ROA: none185.242.177.0/24No ROA covers it. Add a ROA for AS35369, maxLength 24.673 of 673
ROA: none193.104.82.0/24No ROA covers it. Add a ROA for AS35369, maxLength 24.673 of 673
ROA: none193.186.164.0/22No ROA covers it. Add a ROA for AS35369, maxLength 22.673 of 673
ROA: none193.186.168.0/22No ROA covers it. Add a ROA for AS35369, maxLength 22.673 of 673
ROA: none194.116.158.0/23No ROA covers it. Add a ROA for AS35369, maxLength 23.673 of 673
ROA: none2602:810:2081::/48No ROA covers it. Add a ROA for AS35369, maxLength 48.634 of 636

Route objects not announced

Every route object with origin AS35369 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.