bgpreport

Network · data from 2026-11-12

AS57652 ZELTELECOM-AS OOO "Zeltelecom"

Registry name: ZELTELECOM-AS OOO "Zeltelecom", RU · not in PeeringDB

4IPv4 routes 50.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
3No 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 AS57652, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS57652, 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.
178.170.243.0/24 No ROA RIR databaseRIPE 673 100% 66
37.230.147.0/24 No ROA RIR databaseRIPE 672 100% 66
2a03:5a00:28::/48 No ROA RIR databaseRIPE 636 100% 69
141.101.233.0/24 Valid RIR databaseRIPE 673 100% 66
188.72.73.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS57652 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: none3
ChangePrefix or setDetailFull-table peers
ROA: none178.170.243.0/24No ROA covers it. Add a ROA for AS57652, maxLength 24.673 of 673
ROA: none37.230.147.0/24No ROA covers it. Add a ROA for AS57652, maxLength 24.672 of 673
ROA: none2a03:5a00:28::/48No ROA covers it. Add a ROA for AS57652, maxLength 48.636 of 636

Route objects not announced

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