bgpreport

Network · data from 2026-11-12

AS215849 Tristan Klock

Registry name: Tristan-Klock Tristan Klock, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215849, 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:7585::/32 No ROA None 1 0%low visibility 1
2a14:7585:f000::/36 No ROA None 1 0%low visibility 1
5.175.177.0/24 Valid RIR databaseRIPE 673 100% 67
2a07:2486:e000::/36 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS215849: AS215849:AS-TGK. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS215849 isn't in the set, or no route object for AS215849 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS215849 in itNot covered
AS215849:AS-TGK RIPE 125 Yes 2

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

  • ROA: none2
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2a14:7585::/32No ROA covers it. Add a ROA for AS215849, maxLength 32.1 of 636
Route object: none2a14:7585::/32No route object for it. Add a route object with origin AS215849 in the RIR database for the space.1 of 636
ROA: none2a14:7585:f000::/36No ROA covers it. Add a ROA for AS215849, maxLength 36.1 of 636
Route object: none2a14:7585:f000::/36No route object for it. Add a route object with origin AS215849 in the RIR database for the space.1 of 636

Route objects not announced

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

2a0e:b107:27f0::/46RIPENo ROA
2a0e:b107:2830::/46RIPENo ROA
2a0e:b107:2834::/46RIPENo 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.