bgpreport

Network · data from 2026-11-12

AS24708 GRZ-AT RAITEC GmbH

Registry name: GRZ-AT RAITEC GmbH, AT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24708, 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.
194.37.244.254/32 No ROA Nonecovered by 194.37.240.0/21 2 0%low visibility 6
2001:67c:2204:607::2ffa:0/128 No ROA Nonecovered by 2001:67c:2204::/48 1 0%low visibility 4
149.154.103.0/24 No ROA RIR databaseRIPE 673 100% 66
193.17.222.0/24 No ROA RIR databaseRIPE 673 100% 66
193.110.129.0/24 No ROA RIR databaseRIPE 673 100% 66
193.228.16.0/20 No ROA RIR databaseRIPE 673 100% 66
194.37.240.0/21 No ROA RIR databaseRIPE 673 100% 66
194.116.224.0/23 No ROA RIR databaseRIPE 673 100% 66
2001:67c:2204::/48 No ROA RIR databaseRIPE 636 100% 69

AS-SET

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

  • ROA: none9
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none194.37.244.254/32No ROA covers it. Add a ROA for AS24708, maxLength 32.2 of 673
Route object: none194.37.244.254/32No route object for it. A route object for 194.37.240.0/21 with origin AS24708 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24708 in the RIR database for the space.2 of 673
ROA: none2001:67c:2204:607::2ffa:0/128No ROA covers it. Add a ROA for AS24708, maxLength 128.1 of 636
Route object: none2001:67c:2204:607::2ffa:0/128No route object for it. A route object for 2001:67c:2204::/48 with origin AS24708 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS24708 in the RIR database for the space.1 of 636
ROA: none149.154.103.0/24No ROA covers it. Add a ROA for AS24708, maxLength 24.673 of 673
ROA: none193.17.222.0/24No ROA covers it. Add a ROA for AS24708, maxLength 24.673 of 673
ROA: none193.110.129.0/24No ROA covers it. Add a ROA for AS24708, maxLength 24.673 of 673
ROA: none193.228.16.0/20No ROA covers it. Add a ROA for AS24708, maxLength 20.673 of 673
ROA: none194.37.240.0/21No ROA covers it. Add a ROA for AS24708, maxLength 21.673 of 673
ROA: none194.116.224.0/23No ROA covers it. Add a ROA for AS24708, maxLength 23.673 of 673
ROA: none2001:67c:2204::/48No ROA covers it. Add a ROA for AS24708, maxLength 48.636 of 636

Route objects not announced

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