Network · data from 2026-11-12

AS57022 DataVita

Registry name: DATAVITA-AS HFD DATAVITA LIMITED, GB · PeeringDB

12IPv4 routes 75.0% RPKI valid · 100.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

4No ROA 1 with no route object for this origin

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

2Route objects not announced registered with origin AS57022, seen from no peer

Announced routes

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


2a05:2b00:1::/48	No ROA	Nonecovered by 2a05:2b00::/29	635 100%	68
185.70.168.0/22	No ROA	RIR databaseRIPE	672 100%	67
194.45.181.0/24	No ROA	RIR databaseRIPE	672 100%	67
193.35.31.0/24	No ROA	RIR databaseRIPE	671 100%	67
194.45.45.0/24	Valid	RIR databaseRIPE	673 100%	67
194.45.106.0/24	Valid	RIR databaseRIPE	673 100%	67
185.70.168.0/24	Valid	RIR databaseRIPE	672 100%	67
185.70.169.0/24	Valid	RIR databaseRIPE	672 100%	67
185.70.170.0/24	Valid	RIR databaseRIPE	672 100%	67
185.70.171.0/24	Valid	RIR databaseRIPE	672 100%	67
194.45.169.0/24	Valid	RIR databaseRIPE	672 100%	67
193.35.28.0/23	Valid	RIR databaseRIPE	671 100%	67
193.35.30.0/24	Valid	RIR databaseRIPE	671 100%	67

AS-SET

AS57022's PeeringDB record names no 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 7 are in fix.csv.

ROA: none4
Route object: none1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: none	2a05:2b00:1::/48	No ROA covers it. Add a ROA for AS57022, maxLength 48.	635 of 636
Route object: none	2a05:2b00:1::/48	No route object for it. A route object for 2a05:2b00::/29 with origin AS57022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57022 in the RIR database for the space.	635 of 636
ROA: none	185.70.168.0/22	No ROA covers it. Add a ROA for AS57022, maxLength 22.	672 of 673
ROA: none	194.45.181.0/24	No ROA covers it. Add a ROA for AS57022, maxLength 24.	672 of 673
ROA: none	193.35.31.0/24	No ROA covers it. Add a ROA for AS57022, maxLength 24.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

2a05:2b00:1::/48

No ROA covers it. Add a ROA for AS57022, maxLength 48.

635 of 636

Route object: none

2a05:2b00:1::/48

No route object for it. A route object for 2a05:2b00::/29 with origin AS57022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57022 in the RIR database for the space.

635 of 636

ROA: none

185.70.168.0/22

No ROA covers it. Add a ROA for AS57022, maxLength 22.

672 of 673

ROA: none

194.45.181.0/24

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

672 of 673

ROA: none

193.35.31.0/24

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

671 of 673

Route objects not announced

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


193.35.28.0/22	RIPE	No ROA
2a05:2b00::/29	RIPE	No ROA

193.35.28.0/22

RIPE

No ROA

2a05:2b00::/29

RIPE

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