bgpreport

Network · data from 2026-11-12

AS16205 DSI NET

Registry name: DSINET-ASN DSI GmbH Daten Service Informationssysteme, DE · PeeringDB

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

Announced routes

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

192.109.108.0/24 No ROA RIR databaseRIPE 673 100% 66
194.31.246.0/24 No ROA RIR databaseRIPE 673 100% 66
194.113.71.0/24 No ROA RIR databaseRIPE 673 100% 66
194.180.239.0/24 No ROA RIR databaseRIPE 673 100% 66
2001:67c:2abc::/48 No ROA RIR databaseRIPE 636 100% 67
31.210.160.0/21 Valid RIR databaseRIPE 673 100% 66
81.201.144.0/20 Valid RIR databaseRIPE 673 100% 66
176.52.200.0/21 Valid RIR databaseRIPE 673 100% 66
178.249.24.0/21 Valid RIR databaseRIPE 673 100% 66
185.75.184.0/22 Valid RIR databaseRIPE 673 100% 66
217.18.176.0/20 Valid RIR databaseRIPE 673 100% 66
2a00:8180::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS16205: RIPE::AS-DSI. 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 (AS16205 isn't in the set, or no route object for AS16205 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 objectsAS16205 in itNot covered
RIPE::AS-DSI RIPE 811,584 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: none5
ChangePrefix or setDetailFull-table peers
ROA: none192.109.108.0/24No ROA covers it. Add a ROA for AS16205, maxLength 24.673 of 673
ROA: none194.31.246.0/24No ROA covers it. Add a ROA for AS16205, maxLength 24.673 of 673
ROA: none194.113.71.0/24No ROA covers it. Add a ROA for AS16205, maxLength 24.673 of 673
ROA: none194.180.239.0/24No ROA covers it. Add a ROA for AS16205, maxLength 24.673 of 673
ROA: none2001:67c:2abc::/48No ROA covers it. Add a ROA for AS16205, maxLength 48.636 of 636

Route objects not announced

Every route object with origin AS16205 is announced.

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.