bgpreport

Network · data from 2026-11-12

AS43440 Digitale Suisse

Registry name: digitalesuisse Digitale Suisse AG, CH · PeeringDB

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

Announced routes

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

179.43.128.0/18 No ROA Other origin only 2 0%low visibility 2
185.227.148.0/24 No ROA Other IRR onlyRADB 671 100% 68
185.227.149.0/24 No ROA Other IRR onlyRADB 671 100% 67
185.227.150.0/24 No ROA Other IRR onlyRADB 671 100% 68
185.227.151.0/24 No ROA Other IRR onlyRADB 671 100% 67
176.105.235.0/24 No ROA Other IRR onlyRADB 0 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS43440: AS-DIGITALESUISSE. 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 (AS43440 isn't in the set, or no route object for AS43440 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 objectsAS43440 in itNot covered
AS-DIGITALESUISSE RADB 221520 Yes 1

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

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none179.43.128.0/18No ROA covers it. Add a ROA for AS43440, maxLength 18.2 of 673
Route object: none179.43.128.0/18Route objects for it name AS51852. Add a route object with origin AS43440 in the RIR database for the space.2 of 673
ROA: none185.227.148.0/24No ROA covers it. Add a ROA for AS43440, maxLength 24.671 of 673
Route object: RIR185.227.148.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none185.227.149.0/24No ROA covers it. Add a ROA for AS43440, maxLength 24.671 of 673
Route object: RIR185.227.149.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none185.227.150.0/24No ROA covers it. Add a ROA for AS43440, maxLength 24.671 of 673
Route object: RIR185.227.150.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none185.227.151.0/24No ROA covers it. Add a ROA for AS43440, maxLength 24.671 of 673
Route object: RIR185.227.151.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none176.105.235.0/24No ROA covers it. Add a ROA for AS43440, maxLength 24.0 of 673
Route object: RIR176.105.235.0/24Route object only in RADB. Add it in the RIR database for the space.0 of 673

Route objects not announced

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

2001:470:2bd::/48ARINValid
2001:470:645::/48ARINValid
2a10:83c0::/32RADBNo ROA
2a10:83c1::/32RADBNo ROA
2a10:83c2::/32RADBNo ROA
2a10:83c3::/32RADBNo ROA
2a10:83c4::/32RADBNo ROA
2a10:83c5::/32RADBNo ROA
2a10:83c6::/32RADBNo ROA
2a10:83c7::/32RADBNo 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.