Network · data from 2026-11-12

AS41443 SMART-TELEKOM-AS OOO SMART-TELEKOM

Registry name: SMART-TELEKOM-AS OOO SMART-TELEKOM, RU · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

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

Announced routes

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


89.31.16.0/21	No ROA	RIR databaseRIPE	671 100%	68

89.31.16.0/21

No ROA

RIR databaseRIPE

671 100%

AS-SET

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

ROA: none1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: none	89.31.16.0/21	No ROA covers it. Add a ROA for AS41443, maxLength 21.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

89.31.16.0/21

No ROA covers it. Add a ROA for AS41443, maxLength 21.

671 of 673

Route objects not announced

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


89.31.16.0/27	RIPE	No ROA
89.31.16.32/27	RIPE	No ROA

89.31.16.0/27

RIPE

No ROA

89.31.16.32/27

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.