Network · data from 2026-11-12

AS198333 DATAGROUP-AS DATAGROUP SE

Registry name: DATAGROUP-AS DATAGROUP SE, DE · not in PeeringDB

14IPv4 routes 78.6% 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

4No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS198333, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS198333, 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.55.152.0/24	No ROA	RIR databaseRIPE	673 100%	67
185.55.153.0/24	No ROA	RIR databaseRIPE	673 100%	67
185.55.154.0/24	No ROA	RIR databaseRIPE	673 100%	67
2a0b:3180::/29	No ROA	RIR databaseRIPE	634 100%	68
91.217.141.0/24	Valid	RIR databaseRIPE	673 100%	67
176.123.51.0/24	Valid	RIR databaseRIPE	673 100%	67
185.184.100.0/22	Valid	RIR databaseRIPE	673 100%	67
185.184.100.0/24	Valid	RIR databaseRIPE	673 100%	67
185.184.102.0/24	Valid	RIR databaseRIPE	673 100%	67
185.184.103.0/24	Valid	RIR databaseRIPE	673 100%	67
193.37.149.0/24	Valid	RIR databaseRIPE	673 100%	67
194.139.6.0/23	Valid	RIR databaseRIPE	673 100%	67
194.139.6.0/24	Valid	RIR databaseRIPE	673 100%	67
194.139.7.0/24	Valid	RIR databaseRIPE	673 100%	67
195.66.99.0/24	Valid	RIR databaseRIPE	673 100%	67
2001:67c:1988::/48	Valid	RIR databaseRIPE	635 100%	68

AS-SET

AS198333 isn't in PeeringDB, where networks name their AS-SET.

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: none4
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	185.55.152.0/24	No ROA covers it. Add a ROA for AS198333, maxLength 24.	673 of 673
ROA: none	185.55.153.0/24	No ROA covers it. Add a ROA for AS198333, maxLength 24.	673 of 673
ROA: none	185.55.154.0/24	No ROA covers it. Add a ROA for AS198333, maxLength 24.	673 of 673
ROA: none	2a0b:3180::/29	No ROA covers it. Add a ROA for AS198333, maxLength 29.	634 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

185.55.152.0/24

No ROA covers it. Add a ROA for AS198333, maxLength 24.

673 of 673

ROA: none

185.55.153.0/24

No ROA covers it. Add a ROA for AS198333, maxLength 24.

673 of 673

ROA: none

185.55.154.0/24

No ROA covers it. Add a ROA for AS198333, maxLength 24.

673 of 673

ROA: none

2a0b:3180::/29

No ROA covers it. Add a ROA for AS198333, maxLength 29.

634 of 636

Route objects not announced

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


185.184.101.0/24	RIPE	Valid

185.184.101.0/24

RIPE

Valid

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.