bgpreport

Network · data from 2026-11-12

AS47409 TPI-AS thinkproject Deutschland GmbH

Registry name: TPI-AS thinkproject Deutschland GmbH, DE · not in PeeringDB

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

Announced routes

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

93.191.211.0/24 No ROA Nonecovered by 93.191.208.0/21 672 100% 66
93.191.213.0/24 No ROA Nonecovered by 93.191.208.0/21 672 100% 66
93.191.208.0/24 No ROA RIR databaseRIPE 672 100% 66
93.191.209.0/24 No ROA RIR databaseRIPE 672 100% 66
93.191.210.0/24 No ROA RIR databaseRIPE 672 100% 66
93.191.214.0/24 No ROA RIR databaseRIPE 672 100% 66
93.191.215.0/24 No ROA RIR databaseRIPE 672 100% 66

AS-SET

AS47409 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none93.191.211.0/24No ROA covers it. Add a ROA for AS47409, maxLength 24.672 of 673
Route object: none93.191.211.0/24No route object for it. A route object for 93.191.208.0/21 with origin AS47409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47409 in the RIR database for the space.672 of 673
ROA: none93.191.213.0/24No ROA covers it. Add a ROA for AS47409, maxLength 24.672 of 673
Route object: none93.191.213.0/24No route object for it. A route object for 93.191.208.0/21 with origin AS47409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47409 in the RIR database for the space.672 of 673
ROA: none93.191.208.0/24No ROA covers it. Add a ROA for AS47409, maxLength 24.672 of 673
ROA: none93.191.209.0/24No ROA covers it. Add a ROA for AS47409, maxLength 24.672 of 673
ROA: none93.191.210.0/24No ROA covers it. Add a ROA for AS47409, maxLength 24.672 of 673
ROA: none93.191.214.0/24No ROA covers it. Add a ROA for AS47409, maxLength 24.672 of 673
ROA: none93.191.215.0/24No ROA covers it. Add a ROA for AS47409, maxLength 24.672 of 673

Route objects not announced

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

93.191.208.0/21RIPENo ROA
2a03:9d00::/32RIPENo ROA
2a03:9d00::/48RIPENo ROA
2a03:9d00:80::/48RIPENo ROA
2a03:9d00:f0::/48RIPENo 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.