Network · data from 2026-11-12

AS25446 ERTH-CLOUD-AS JSC "ER-Telecom Holding"

Registry name: ERTH-CLOUD-AS JSC "ER-Telecom Holding", RU · not in PeeringDB

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

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

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

Announced routes

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


77.106.68.0/22	Valid	RIR databaseRIPE	673 100%	66
93.183.104.0/24	Valid	RIR databaseRIPE	673 100%	66
93.183.105.0/24	Valid	RIR databaseRIPE	673 100%	66
93.183.106.0/24	Valid	RIR databaseRIPE	673 100%	66
93.183.107.0/24	Valid	RIR databaseRIPE	673 100%	66
185.71.196.0/24	Valid	RIR databaseRIPE	673 100%	66
2001:67c:1584::/48	Valid	RIR databaseRIPE	636 100%	68
2a03:e340:3::/48	Valid	RIR databaseRIPE	636 100%	68
2a0c:c580::/48	Valid	RIR databaseRIPE	636 100%	68

AS-SET

AS25446 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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