bgpreport

Network · data from 2026-11-12

AS44166 NTD

Registry name: NTD-AS NTD SA, CH · PeeringDB

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

Announced routes

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

79.141.92.0/24 Valid Nonecovered by 79.141.80.0/20 673 100% 67
79.141.94.0/24 Valid Nonecovered by 79.141.80.0/20 673 100% 67
2a05:dac0::/32 Valid Nonecovered by 2a05:dac0::/29 605 95% 67
2a05:dac0:2::/48 Valid Nonecovered by 2a05:dac0::/29 605 95% 67
2a05:dac0:3::/48 Valid Nonecovered by 2a05:dac0::/29 605 95% 67
2a05:dac3::/32 Valid Nonecovered by 2a05:dac0::/29 605 95% 67
2a05:dac0:1::/48 Valid Nonecovered by 2a05:dac0::/29 604 95% 67
2a05:dac1::/32 Valid Nonecovered by 2a05:dac0::/29 604 95% 67
2a05:dac2::/32 Valid Nonecovered by 2a05:dac0::/29 604 95% 67
2a05:dac4::/32 Valid Nonecovered by 2a05:dac0::/29 604 95% 67
2a05:dac5::/32 Valid Nonecovered by 2a05:dac0::/29 604 95% 67
2a05:dac6::/32 Valid Nonecovered by 2a05:dac0::/29 604 95% 67
2a05:dac7::/32 Valid Nonecovered by 2a05:dac0::/29 604 95% 67
79.141.80.0/20 Valid RIR databaseRIPE 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS44166: AS44166. 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 (AS44166 isn't in the set, or no route object for AS44166 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 objectsAS44166 in itNot covered
AS44166 A single AS number, not a set: AS44166 (this network), 2 route objects.

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

  • Route object: none13
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none79.141.92.0/24No route object for it. A route object for 79.141.80.0/20 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.673 of 673
Route object: none79.141.94.0/24No route object for it. A route object for 79.141.80.0/20 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.673 of 673
Route object: none2a05:dac0::/32No route object for it. A route object for 2a05:dac0::/29 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.605 of 636
Route object: none2a05:dac0:2::/48No route object for it. A route object for 2a05:dac0::/29 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.605 of 636
Route object: none2a05:dac0:3::/48No route object for it. A route object for 2a05:dac0::/29 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.605 of 636
Route object: none2a05:dac3::/32No route object for it. A route object for 2a05:dac0::/29 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.605 of 636
Route object: none2a05:dac0:1::/48No route object for it. A route object for 2a05:dac0::/29 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.604 of 636
Route object: none2a05:dac1::/32No route object for it. A route object for 2a05:dac0::/29 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.604 of 636
Route object: none2a05:dac2::/32No route object for it. A route object for 2a05:dac0::/29 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.604 of 636
Route object: none2a05:dac4::/32No route object for it. A route object for 2a05:dac0::/29 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.604 of 636
Route object: none2a05:dac5::/32No route object for it. A route object for 2a05:dac0::/29 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.604 of 636
Route object: none2a05:dac6::/32No route object for it. A route object for 2a05:dac0::/29 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.604 of 636
Route object: none2a05:dac7::/32No route object for it. A route object for 2a05:dac0::/29 with origin AS44166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44166 in the RIR database for the space.604 of 636

Route objects not announced

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

2a05:dac0::/29RIPENo 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.