Network · data from 2026-11-12

AS210967 indasys IT Systemhaus AG

Registry name: ASN-INDASYS indasys IT Systemhaus AG, DE · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No 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 AS210967, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS210967, 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.19.200.0/24	Valid	RIR databaseRIPE	673 100%	66
193.0.199.0/24	Valid	RIR databaseRIPE	673 100%	66
213.217.30.0/24	Valid	RIR databaseRIPE	673 100%	66
2a11:1b00::/29	Valid	RIR databaseRIPE	633 100%	67

AS-SET

PeeringDB's irr_as_set for AS210967: RIPE::AS210967:AS-INDASYS. 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 (AS210967 isn't in the set, or no route object for AS210967 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.

Name	Database	ASNs	Sets	Route objects	AS210967 in it	Not covered
RIPE::AS210967:AS-INDASYS	RIPE	1	1	4	Yes	0

Name

Database

ASNs

Sets

Route objects

AS210967 in it

Not covered

RIPE::AS210967:AS-INDASYS

RIPE

Yes

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS210967 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.