bgpreport

Network · data from 2026-11-12

AS56679 TECOM-AS Voin Telecom LLC

Registry name: TECOM-AS Voin Telecom LLC, RU · not in PeeringDB

7IPv4 routes 42.9% RPKI valid · 100.0% with a route object
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No 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 AS56679, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS56679, 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.152.220.0/22 No ROA RIR databaseRIPE 671 100% 68
185.143.236.0/24 No ROA RIR databaseRIPE 671 100% 68
194.186.48.0/24 No ROA RIR databaseRIPE 671 100% 68
213.33.244.0/24 No ROA RIR databaseRIPE 671 100% 68
2a0f:6300::/48 No ROA RIR databaseRIPE 636 100% 69
2a14:6c00::/48 No ROA RIR databaseRIPE 636 100% 69
81.3.154.0/24 Valid RIR databaseRIPE 671 100% 68
84.204.148.0/24 Valid RIR databaseRIPE 671 100% 68
85.143.156.0/23 Valid RIR databaseRIPE 671 100% 68

AS-SET

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

  • ROA: none6
ChangePrefix or setDetailFull-table peers
ROA: none45.152.220.0/22No ROA covers it. Add a ROA for AS56679, maxLength 22.671 of 673
ROA: none185.143.236.0/24No ROA covers it. Add a ROA for AS56679, maxLength 24.671 of 673
ROA: none194.186.48.0/24No ROA covers it. Add a ROA for AS56679, maxLength 24.671 of 673
ROA: none213.33.244.0/24No ROA covers it. Add a ROA for AS56679, maxLength 24.671 of 673
ROA: none2a0f:6300::/48No ROA covers it. Add a ROA for AS56679, maxLength 48.636 of 636
ROA: none2a14:6c00::/48No ROA covers it. Add a ROA for AS56679, maxLength 48.636 of 636

Route objects not announced

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