bgpreport

Network · data from 2026-11-12

AS21446 SOTEL

Registry name: AS21446 SOTEL LLC, RU · PeeringDB

3IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No 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 AS21446, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS21446, 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.
78.24.152.0/21 No ROA RIR databaseRIPE 673 100% 66
80.251.128.0/20 No ROA RIR databaseRIPE 673 100% 66
185.113.116.0/22 No ROA RIR databaseRIPE 673 100% 66
2a01:4c80::/32 No ROA RIR databaseRIPE 333 52% 63

AS-SET

AS21446'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 4 are in fix.csv.

  • ROA: none4
ChangePrefix or setDetailFull-table peers
ROA: none78.24.152.0/21No ROA covers it. Add a ROA for AS21446, maxLength 21.673 of 673
ROA: none80.251.128.0/20No ROA covers it. Add a ROA for AS21446, maxLength 20.673 of 673
ROA: none185.113.116.0/22No ROA covers it. Add a ROA for AS21446, maxLength 22.673 of 673
ROA: none2a01:4c80::/32No ROA covers it. Add a ROA for AS21446, maxLength 32.333 of 636

Route objects not announced

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