bgpreport

Network · data from 2026-11-12

AS50136 Comtrend Kurt Schreckenbauer trading as Comtrend

Registry name: Comtrend Kurt Schreckenbauer trading as Comtrend, CH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50136, 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.
185.79.88.0/22 No ROA RIR databaseRIPE 670 100% 67

AS-SET

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

  • ROA: none1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none185.79.88.0/22No ROA covers it. Add a ROA for AS50136, maxLength 22.670 of 673

Route objects not announced

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

188.209.144.0/20RADBNo ROA
188.211.248.0/23RADBNo ROA
188.211.250.0/23RADBNo ROA
188.212.4.0/23RADBNo ROA
188.241.144.0/23RADBNo ROA
188.241.146.0/23RADBNo ROA
188.241.152.0/23RADBNo ROA
188.241.154.0/23RADBNo ROA
188.241.158.0/23RADBNo 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.