Network · data from 2026-11-12

AS212913 TIMEHOST-AS TIME-HOST LTD

Registry name: TIMEHOST-AS TIME-HOST LTD, GB · not in PeeringDB

17IPv4 routes 82.4% RPKI valid · 100.0% with a route object

2IPv6 routes 100.0% RPKI valid · 50.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

3No ROA 1 with no route object for this origin

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

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

Announced routes

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


45.130.151.0/24	No ROA	RIR databaseRIPE	671 100%	68
45.131.46.0/24	No ROA	RIR databaseRIPE	671 100%	68
89.221.206.0/24	No ROA	RIR databaseRIPE	671 100%	68
2001:67c:af4::/48	Valid	Other origin only	635 100%	67
31.148.99.0/24	Valid	RIR databaseRIPE	671 100%	68
45.140.19.0/24	Valid	RIR databaseRIPE	671 100%	68
45.151.139.0/24	Valid	RIR databaseRIPE	671 100%	68
62.3.58.0/24	Valid	RIR databaseRIPE	671 100%	68
80.76.42.0/24	Valid	RIR databaseRIPE	671 100%	68
81.22.193.0/24	Valid	RIR databaseRIPE	671 100%	68
89.221.204.0/24	Valid	RIR databaseRIPE	671 100%	68
91.242.236.0/24	Valid	RIR databaseRIPE	671 100%	68
93.170.123.0/24	Valid	RIR databaseRIPE	671 100%	68
94.103.183.0/24	Valid	RIR databaseRIPE	671 100%	68
130.49.181.0/24	Valid	RIR databaseRIPE	671 100%	68
130.49.186.0/24	Valid	RIR databaseRIPE	671 100%	68
170.168.89.0/24	Valid	RIR databaseRIPE	671 100%	68
193.3.23.0/24	Valid	RIR databaseRIPE	671 100%	68
2a06:1301:4610::/48	Valid	RIR databaseRIPE	636 100%	69

AS-SET

AS212913 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: none3
Route object: none1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	45.130.151.0/24	No ROA covers it. Add a ROA for AS212913, maxLength 24.	671 of 673
ROA: none	45.131.46.0/24	No ROA covers it. Add a ROA for AS212913, maxLength 24.	671 of 673
ROA: none	89.221.206.0/24	No ROA covers it. Add a ROA for AS212913, maxLength 24.	671 of 673
Route object: none	2001:67c:af4::/48	Route objects for it name AS35196. Add a route object with origin AS212913 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

45.130.151.0/24

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

671 of 673

ROA: none

45.131.46.0/24

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

671 of 673

ROA: none

89.221.206.0/24

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

671 of 673

Route object: none

2001:67c:af4::/48

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

635 of 636

Route objects not announced

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


2a14:a402::/32	RIPE	Valid

2a14:a402::/32

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.