bgpreport

Network · data from 2026-11-12

AS47641 FF Florian Fuessl

Registry name: FF Florian Fuessl, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47641, 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.
139.28.60.0/22 Valid RIR databaseRADB, RIPE 671 100% 67

AS-SET

AS47641 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 15 are in fix.csv.

  • Route object: not announced15

Route objects not announced

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

139.28.60.0/23RADB, RIPEValid
139.28.60.0/24RADB, RIPEValid
139.28.61.0/24RADB, RIPEValid
139.28.62.0/23RADB, RIPEValid
139.28.62.0/24RIPEValid
139.28.63.0/24RADB, RIPEValid
2a09:f580::/29RIPEValid
2a09:f580::/32RADBValid
2a09:f581::/32RADBValid
2a09:f582::/32RADBValid
2a09:f583::/32RADBValid
2a09:f584::/32RADBValid
2a09:f585::/32RADBValid
2a09:f586::/32RADBValid
2a09:f587::/32RADBValid

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.