Network · data from 2026-11-12

AS204767 PRIVATE-DATACENTER VIRTUAL PRIVATE SERVER DATACENTER LIMITED

Registry name: PRIVATE-DATACENTER VIRTUAL PRIVATE SERVER DATACENTER LIMITED, GB · not in PeeringDB

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

0IPv6 routes

2RPKI invalid 2 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

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

Announced routes

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


131.222.213.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
153.56.222.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
87.192.40.0/24	Valid	RIR databaseRIPE	673 100%	67

131.222.213.0/24

Invalid: origin

Other origin only

2 0%low visibility

153.56.222.0/24

Invalid: origin

Other origin only

2 0%low visibility

87.192.40.0/24

Valid

RIR databaseRIPE

673 100%

AS-SET

AS204767 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 6 are in fix.csv.

ROA: origin2
Route object: none2
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	131.222.213.0/24	ROAs covering it name AS214095, not AS204767. If AS204767 should announce it, add a ROA for AS204767.	2 of 673
Route object: none	131.222.213.0/24	Route objects for it name AS214095. Add a route object with origin AS204767 in the RIR database for the space.	2 of 673
ROA: origin	153.56.222.0/24	ROAs covering it name AS25198, not AS204767. If AS204767 should announce it, add a ROA for AS204767.	2 of 673
Route object: none	153.56.222.0/24	Route objects for it name AS197710. Add a route object with origin AS204767 in the RIR database for the space.	2 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

131.222.213.0/24

ROAs covering it name AS214095, not AS204767. If AS204767 should announce it, add a ROA for AS204767.

2 of 673

Route object: none

131.222.213.0/24

Route objects for it name AS214095. Add a route object with origin AS204767 in the RIR database for the space.

2 of 673

ROA: origin

153.56.222.0/24

ROAs covering it name AS25198, not AS204767. If AS204767 should announce it, add a ROA for AS204767.

2 of 673

Route object: none

153.56.222.0/24

Route objects for it name AS197710. Add a route object with origin AS204767 in the RIR database for the space.

2 of 673

Route objects not announced

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


199.177.183.0/24	ALTDB	No ROA
2a0f:85c1:d94::/48	RIPE	No ROA

199.177.183.0/24

ALTDB

No ROA

2a0f:85c1:d94::/48

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.