bgpreport

Network · data from 2026-11-12

AS15790 FINANZINFORMATIK-AS-OST Finanz Informatik GmbH & Co. KG

Registry name: FINANZINFORMATIK-AS-OST Finanz Informatik GmbH & Co. KG, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS15790, 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.

62.181.128.0/19 No ROA RIR databaseRIPE 673 100% 66
195.42.254.0/23 No ROA RIR databaseRIPE 673 100% 66
2a02:bb1:1000::/37 No ROA RIR databaseRIPE 635 100% 67
2a02:bb0::/29 No ROA RIR databaseRIPE 218 34% 49

AS-SET

AS15790 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: none4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none62.181.128.0/19No ROA covers it. Add a ROA for AS15790, maxLength 19.673 of 673
ROA: none195.42.254.0/23No ROA covers it. Add a ROA for AS15790, maxLength 23.673 of 673
ROA: none2a02:bb1:1000::/37No ROA covers it. Add a ROA for AS15790, maxLength 37.635 of 636
ROA: none2a02:bb0::/29No ROA covers it. Add a ROA for AS15790, maxLength 29.218 of 636

Route objects not announced

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

62.181.128.0/20RIPENo ROA
62.181.144.0/20RIPENo ROA
62.181.146.0/24RIPENo ROA
2a02:bb0::/32RIPENo 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.