bgpreport

Network · data from 2026-11-12

AS29691 Nine Internet Solutions AG

Registry name: NINE Nine Internet Solutions AG, CH · PeeringDB

12IPv4 routes 91.7% RPKI valid · 91.7% with a route object
4IPv6 routes 75.0% RPKI valid · 75.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
1Route objects not announced registered with origin AS29691, seen from no peer

Announced routes

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

178.209.52.0/24 Invalid: maxLength Nonecovered by 178.209.32.0/19 1 0%low visibility 1
2a02:418:6a04::/48 Invalid: maxLength Nonecovered by 2a02:418::/29 1 0%low visibility 1
203.56.112.0/23 Valid RIR databaseRIPE 673 100% 67
45.9.160.0/24 Valid RIR databaseRIPE 672 100% 67
45.9.161.0/24 Valid RIR databaseRIPE 672 100% 67
45.9.162.0/24 Valid RIR databaseRIPE 672 100% 67
5.148.160.0/19 Valid RIR databaseRIPE 670 100% 67
92.42.184.0/21 Valid RIR databaseRIPE 670 100% 67
94.230.208.0/20 Valid RIR databaseRIPE 670 100% 67
178.209.32.0/19 Valid RIR databaseRIPE 670 100% 67
185.88.236.0/22 Valid RIR databaseRIPE 670 100% 67
193.17.85.0/24 Valid RIR databaseRIPE 670 100% 67
217.150.240.0/20 Valid RIR databaseRIPE 670 100% 67
2a14:3e40::/32 Valid RIR databaseRIPE 635 100% 69
2001:67c:2f98::/48 Valid RIR databaseRIPE 634 100% 69
2a02:418::/29 Valid RIR databaseRIPE 633 100% 69

AS-SET

PeeringDB's irr_as_set for AS29691: AS-NINE. 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 (AS29691 isn't in the set, or no route object for AS29691 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 objectsAS29691 in itNot covered
AS-NINE RIPElists itself further down 4127616 Yes 0

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

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength178.209.52.0/24ROA 178.209.32.0/19 AS29691 has maxLength 19; the route is a /24. Raise the maxLength, or add a ROA for 178.209.52.0/24.1 of 673
Route object: none178.209.52.0/24No route object for it. A route object for 178.209.32.0/19 with origin AS29691 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29691 in the RIR database for the space.1 of 673
ROA: maxLength2a02:418:6a04::/48ROA 2a02:418::/29 AS29691 has maxLength 29; the route is a /48. Raise the maxLength, or add a ROA for 2a02:418:6a04::/48.1 of 636
Route object: none2a02:418:6a04::/48No route object for it. A route object for 2a02:418::/29 with origin AS29691 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29691 in the RIR database for the space.1 of 636

Route objects not announced

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

176.223.119.0/24RIPENo 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.