bgpreport

Network · data from 2026-11-12

AS206228 Andritz

Registry name: ANDRITZ01 Andritz AG, AT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206228, 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.
143.161.0.0/16 No ROA RIR databaseRIPE 673 100% 66
185.77.252.0/23 Valid RIR databaseRIPE 673 100% 66
185.77.254.0/23 Valid RIR databaseRIPE 673 100% 66
2a05:6740:4060::/46 Valid RIR databaseRIPE 636 100% 69
2a05:6740:40c0::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

AS206228's PeeringDB record names no 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: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none143.161.0.0/16No ROA covers it. Add a ROA for AS206228, maxLength 16.673 of 673

Route objects not announced

Route objects with origin AS206228 whose prefix no peer sees AS206228 announce. Many are kept on purpose (backup routes, space announced only in some places).

143.161.177.0/24RIPENo ROA
143.161.248.0/24RIPENo ROA
2a05:6740::/29RIPENo 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.