bgpreport

Network · data from 2026-11-12

AS44417 NEOTELECOM-AS JSC Neotelecom

Registry name: NEOTELECOM-AS JSC Neotelecom, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44417, 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.
79.136.224.0/21 No ROA RIR databaseRIPE 673 100% 66
83.172.40.0/22 No ROA RIR databaseRIPE 673 100% 66
46.166.192.0/21 Valid RIR databaseRIPE 673 100% 66
46.166.200.0/21 Valid RIR databaseRIPE 673 100% 66
46.166.208.0/21 Valid RIR databaseRIPE 673 100% 66
46.166.220.0/22 Valid RIR databaseRIPE 673 100% 66
46.166.224.0/22 Valid RIR databaseRIPE 673 100% 66
2a04:3800::/48 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS44417 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 2 are in fix.csv.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none79.136.224.0/21No ROA covers it. Add a ROA for AS44417, maxLength 21.673 of 673
ROA: none83.172.40.0/22No ROA covers it. Add a ROA for AS44417, maxLength 22.673 of 673

Route objects not announced

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