bgpreport

Network · data from 2026-11-12

AS8794 FAZ Frankfurter Allgemeine Zeitung GmbH

Registry name: FAZ Frankfurter Allgemeine Zeitung GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8794, 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.227.159.0/24 No ROA Nonecovered by 193.227.144.0/20 673 100% 66
2001:678:b78::/49 No ROA Nonecovered by 2001:678:b78::/48 8 1%low visibility 5
2001:678:b78:8000::/49 No ROA Nonecovered by 2001:678:b78::/48 8 1%low visibility 5
193.227.144.0/20 No ROA RIR databaseRIPE 673 100% 66
2001:678:b78::/48 No ROA RIR databaseRIPE 636 100% 67

AS-SET

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

  • ROA: none5
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none193.227.159.0/24No ROA covers it. Add a ROA for AS8794, maxLength 24.673 of 673
Route object: none193.227.159.0/24No route object for it. A route object for 193.227.144.0/20 with origin AS8794 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8794 in the RIR database for the space.673 of 673
ROA: none2001:678:b78::/49No ROA covers it. Add a ROA for AS8794, maxLength 49.8 of 636
Route object: none2001:678:b78::/49No route object for it. A route object for 2001:678:b78::/48 with origin AS8794 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS8794 in the RIR database for the space.8 of 636
ROA: none2001:678:b78:8000::/49No ROA covers it. Add a ROA for AS8794, maxLength 49.8 of 636
Route object: none2001:678:b78:8000::/49No route object for it. A route object for 2001:678:b78::/48 with origin AS8794 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS8794 in the RIR database for the space.8 of 636
ROA: none193.227.144.0/20No ROA covers it. Add a ROA for AS8794, maxLength 20.673 of 673
ROA: none2001:678:b78::/48No ROA covers it. Add a ROA for AS8794, maxLength 48.636 of 636

Route objects not announced

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