Network · data from 2026-11-12

AS206286 1of1 Servers

Registry name: ONEOF1SERVERS 1 of 1 Servers Corp, US · PeeringDB

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

0IPv6 routes

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 AS206286, seen from no peer

Announced routes

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


212.189.58.0/24	Valid	Other IRR onlyRADB	668 99%	67
151.242.75.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
62.68.68.0/24	Valid	RIR databaseRIPE	672 100%	70
89.31.216.0/24	Valid	RIR databaseRIPE	672 100%	70
143.20.58.0/24	Valid	RIR databaseRADB, RIPE	672 100%	66
178.239.199.0/24	Valid	RIR databaseRADB, RIPE	672 100%	70
45.141.24.0/24	Valid	RIR databaseRADB, RIPE	671 100%	70
45.144.225.0/24	Valid	RIR databaseRADB, RIPE	671 100%	66
31.56.71.0/24	Valid	RIR databaseRADB, RIPE	668 99%	67
109.122.16.0/24	Valid	RIR databaseRADB, RIPE	665 99%	67
143.20.184.0/24	Valid	RIR databaseRADB, RIPE	661 98%	67

AS-SET

AS206286'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 1 are in fix.csv.

Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	212.189.58.0/24	Route object only in RADB. Add it in the RIR database for the space.	668 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

212.189.58.0/24

Route object only in RADB. Add it in the RIR database for the space.

668 of 673

Route objects not announced

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