bgpreport

Network · data from 2026-11-12

AS204038 ADITSYSTEMS

Registry name: ADITSYSTEMS AD IT Systems GmbH, DE · PeeringDB

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

Announced routes

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

185.115.176.0/22 No ROA RIR databaseRIPE 673 100% 66
2a02:74a0:1::/48 No ROA RIR databaseRIPE 636 100% 67
2a02:74a0:a000::/40 No ROA RIR databaseRIPE 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS204038: AS-ADITSYSTEMS. 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 (AS204038 isn't in the set, or no route object for AS204038 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 objectsAS204038 in itNot covered
AS-ADITSYSTEMS RIPE 115 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: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none185.115.176.0/22No ROA covers it. Add a ROA for AS204038, maxLength 22.673 of 673
ROA: none2a02:74a0:1::/48No ROA covers it. Add a ROA for AS204038, maxLength 48.636 of 636
ROA: none2a02:74a0:a000::/40No ROA covers it. Add a ROA for AS204038, maxLength 40.636 of 636

Route objects not announced

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

2a02:74a0:a008::/48RIPENo ROA
2a02:74a0:a009::/48RIPENo 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.