bgpreport

Network · data from 2026-11-12

AS21039 E-STEIERMARK-ASN Energie Steiermark AG

Registry name: E-STEIERMARK-ASN Energie Steiermark AG, AT · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 75.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
4No 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 AS21039, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS21039, 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.
193.186.222.0/24 No ROA Nonecovered by 193.186.216.0/21 673 100% 66
193.186.216.0/21 No ROA RIR databaseRIPE 673 100% 66
193.186.224.0/20 No ROA RIR databaseRIPE 673 100% 66
193.186.225.0/24 No ROA RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: none4
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none193.186.222.0/24No ROA covers it. Add a ROA for AS21039, maxLength 24.673 of 673
Route object: none193.186.222.0/24No route object for it. A route object for 193.186.216.0/21 with origin AS21039 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21039 in the RIR database for the space.673 of 673
ROA: none193.186.216.0/21No ROA covers it. Add a ROA for AS21039, maxLength 21.673 of 673
ROA: none193.186.224.0/20No ROA covers it. Add a ROA for AS21039, maxLength 20.673 of 673
ROA: none193.186.225.0/24No ROA covers it. Add a ROA for AS21039, maxLength 24.673 of 673

Route objects not announced

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