bgpreport

Network · data from 2026-11-12

AS39040 NTS Workspace AG AS39040

Registry name: NTSWorkspaceAG-AS39040 NTS workspace AG, CH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39040, 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.
194.187.91.5/32 Invalid: maxLength Nonecovered by 194.187.90.0/23 2 0%low visibility 2
194.187.91.6/32 Invalid: maxLength Nonecovered by 194.187.90.0/23 2 0%low visibility 2
2a02:388:1:200::5/128 Invalid: maxLength Nonecovered by 2a02:388::/32 0 0%low visibility 1
194.187.88.0/22 Valid RIR databaseRIPE 673 100% 67
2a02:388::/32 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS39040: RIPE::AS39040:AS-NTS. 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 (AS39040 isn't in the set, or no route object for AS39040 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 objectsAS39040 in itNot covered
RIPE::AS39040:AS-NTS RIPElists itself further down 2524113 Yes 3

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

  • ROA: maxLength3
  • Route object: none3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength194.187.91.5/32ROA 194.187.88.0/22 AS39040 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 194.187.91.5/32.2 of 673
Route object: none194.187.91.5/32No route object for it. A route object for 194.187.90.0/23 with origin AS39040 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS39040 in the RIR database for the space.2 of 673
ROA: maxLength194.187.91.6/32ROA 194.187.88.0/22 AS39040 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 194.187.91.6/32.2 of 673
Route object: none194.187.91.6/32No route object for it. A route object for 194.187.90.0/23 with origin AS39040 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS39040 in the RIR database for the space.2 of 673
ROA: maxLength2a02:388:1:200::5/128ROA 2a02:388::/32 AS39040 has maxLength 32; the route is a /128. Raise the maxLength, or add a ROA for 2a02:388:1:200::5/128.0 of 636
Route object: none2a02:388:1:200::5/128No route object for it. A route object for 2a02:388::/32 with origin AS39040 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS39040 in the RIR database for the space.0 of 636

Route objects not announced

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

194.187.89.0/24RIPEValid
194.187.90.0/23RIPEInvalid: maxLength
2a02:388:ffff::/48RIPEValid

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.