bgpreport

Network · data from 2026-11-12

AS198311 FBB Flughafen Berlin Brandenburg GmbH

Registry name: FBB Flughafen Berlin Brandenburg GmbH, DE · not in PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.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
5Route objects not announced registered with origin AS198311, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS198311, 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.
2a14:e880::/29 No ROA RIR databaseRIPE 624 98% 67
194.174.72.0/24 Valid RIR databaseRIPE 673 100% 67
194.174.73.0/24 Valid RIR databaseRIPE 673 100% 67
194.174.74.0/24 Valid RIR databaseRIPE 673 100% 67
194.174.75.0/24 Valid RIR databaseRIPE 673 100% 67
194.174.76.0/24 Valid RIR databaseRIPE 673 100% 67
194.174.77.0/24 Valid RIR databaseRIPE 673 100% 67
194.174.79.0/24 Valid RIR databaseRIPE 673 100% 67
195.93.198.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2a14:e880::/29No ROA covers it. Add a ROA for AS198311, maxLength 29.624 of 636

Route objects not announced

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

194.174.72.0/21RIPENo ROA
195.93.198.0/23RIPENo ROA
195.93.199.0/24RIPENo ROA
2001:67c:2880::/48RIPENo ROA
2a14:e880:600::/64RIPENo 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.