bgpreport

Network · data from 2026-11-12

AS15743 net.DE AG

Registry name: NETDE net.de AG, DE · PeeringDB

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

Announced routes

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

94.100.135.0/24 No ROA RIR databaseRIPE 673 100% 66
192.54.43.0/24 No ROA RIR databaseRIPE 673 100% 66
192.109.227.0/24 No ROA RIR databaseRIPE 673 100% 66
193.96.28.0/24 No ROA RIR databaseRIPE 673 100% 66
193.99.145.0/24 No ROA RIR databaseRIPE 673 100% 66
193.100.232.0/24 No ROA RIR databaseRIPE 673 100% 66
193.141.98.0/23 No ROA RIR databaseRIPE 673 100% 66
193.186.12.0/24 No ROA RIR databaseRIPE 673 100% 66
2a01:6780:1::/48 No ROA RIR databaseRIPE 635 100% 69
62.48.88.15/32 Valid Nonecovered by 62.48.64.0/19 2 0%low visibility 6
37.131.240.0/21 Valid RIR databaseRIPE 673 100% 66
62.48.64.0/19 Valid RIR databaseRIPE 673 100% 66
192.166.167.0/24 Valid RIR databaseRIPE 673 100% 66
192.166.176.0/21 Valid RIR databaseRIPE 673 100% 66
193.35.198.0/23 Valid RIR databaseRIPE 673 100% 66
193.35.218.0/23 Valid RIR databaseRIPE 673 100% 67
193.35.218.0/24 Valid RIR databaseRIPE 673 100% 67
193.35.219.0/24 Valid RIR databaseRIPE 673 100% 67
193.98.1.0/24 Valid RIR databaseRIPE 673 100% 66
217.26.224.0/21 Valid RIR databaseRIPE 673 100% 66
2a00:e68::/29 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS15743: AS-NETDE. 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 (AS15743 isn't in the set, or no route object for AS15743 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 objectsAS15743 in itNot covered
AS-NETDE RIPE 7147 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 11 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none94.100.135.0/24No ROA covers it. Add a ROA for AS15743, maxLength 24.673 of 673
ROA: none192.54.43.0/24No ROA covers it. Add a ROA for AS15743, maxLength 24.673 of 673
ROA: none192.109.227.0/24No ROA covers it. Add a ROA for AS15743, maxLength 24.673 of 673
ROA: none193.96.28.0/24No ROA covers it. Add a ROA for AS15743, maxLength 24.673 of 673
ROA: none193.99.145.0/24No ROA covers it. Add a ROA for AS15743, maxLength 24.673 of 673
ROA: none193.100.232.0/24No ROA covers it. Add a ROA for AS15743, maxLength 24.673 of 673
ROA: none193.141.98.0/23No ROA covers it. Add a ROA for AS15743, maxLength 23.673 of 673
ROA: none193.186.12.0/24No ROA covers it. Add a ROA for AS15743, maxLength 24.673 of 673
ROA: none2a01:6780:1::/48No ROA covers it. Add a ROA for AS15743, maxLength 48.635 of 636
Route object: none62.48.88.15/32No route object for it. A route object for 62.48.64.0/19 with origin AS15743 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS15743 in the RIR database for the space.2 of 673

Route objects not announced

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

194.45.127.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.