bgpreport

Network · data from 2026-11-12

AS211540 KSGR

Registry name: KSGR Stiftung Kantonsspital Graubuenden, CH · PeeringDB

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

Announced routes

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

195.242.204.0/32 Invalid: maxLength Nonecovered by 195.242.204.0/24 2 0%low visibility 6
2a14:6d40::/128 Invalid: maxLength Nonecovered by 2a14:6d40::/29 1 0%low visibility 3
195.242.204.0/23 Valid RIR databaseRIPE 672 100% 67
213.177.190.0/24 Valid RIR databaseRIPE 672 100% 67
2a14:6d40::/29 Valid RIR databaseRIPE 632 99% 68

AS-SET

PeeringDB's irr_as_set for AS211540: AS211540:AS-KSGR. 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 (AS211540 isn't in the set, or no route object for AS211540 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 objectsAS211540 in itNot covered
AS211540:AS-KSGR RIPE 115 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 6 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength195.242.204.0/32ROA 195.242.204.0/23 AS211540 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 195.242.204.0/32.2 of 673
Route object: none195.242.204.0/32No route object for it. A route object for 195.242.204.0/24 with origin AS211540 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS211540 in the RIR database for the space.2 of 673
ROA: maxLength2a14:6d40::/128ROA 2a14:6d40::/29 AS211540 has maxLength 32; the route is a /128. Raise the maxLength, or add a ROA for 2a14:6d40::/128.1 of 636
Route object: none2a14:6d40::/128No route object for it. A route object for 2a14:6d40::/29 with origin AS211540 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS211540 in the RIR database for the space.1 of 636

Route objects not announced

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

195.242.204.0/24RIPEValid
195.242.205.0/24RIPEValid

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.