Network · data from 2026-11-12

AS204427 TWC-US Timeweb, LLP

Registry name: TWC-US Timeweb, LLP, KZ · not in PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

6Route objects not announced registered with origin AS204427, seen from no peer

Announced routes

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


72.56.94.0/24	Valid	Other origin only	419 62%	63
186.246.16.0/24	Valid	RIR databaseRIPE	673 100%	67
186.246.17.0/24	Valid	RIR databaseRIPE	673 100%	67
186.246.18.0/24	Valid	RIR databaseRIPE	673 100%	67
186.246.19.0/24	Valid	RIR databaseRIPE	673 100%	67
186.246.20.0/24	Valid	RIR databaseRIPE	673 100%	67
186.246.21.0/24	Valid	RIR databaseRIPE	673 100%	67
186.246.22.0/24	Valid	RIR databaseRIPE	673 100%	67
186.246.23.0/24	Valid	RIR databaseRIPE	673 100%	67
72.56.40.0/24	Valid	RIR databaseRIPE	672 100%	67
72.56.41.0/24	Valid	RIR databaseRIPE	672 100%	67
2a03:6f00:16::/48	Valid	RIR databaseRIPE	636 100%	68

AS-SET

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

Route object: none1
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
Route object: none	72.56.94.0/24	Route objects for it name AS210976. Add a route object with origin AS204427 in the RIR database for the space.	419 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

72.56.94.0/24

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

419 of 673

Route objects not announced

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


200.169.186.0/24	RIPE	Valid
200.169.187.0/24	RIPE	Valid
201.24.58.0/24	RIPE	Valid
201.24.59.0/24	RIPE	Valid
201.51.14.0/24	RIPE	Valid
201.51.15.0/24	RIPE	Valid

200.169.186.0/24

RIPE

Valid

200.169.187.0/24

RIPE

Valid

201.24.58.0/24

RIPE

Valid

201.24.59.0/24

RIPE

Valid

201.51.14.0/24

RIPE

Valid

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