bgpreport

Network · data from 2026-11-12

AS51764 AMTEL-AS JSC AMTEL-SVYAZ

Registry name: AMTEL-AS JSC AMTEL-SVYAZ, RU · not in PeeringDB

29IPv4 routes 93.1% RPKI valid · 37.9% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 18 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS51764, seen from no peer

Announced routes

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

194.226.6.0/24 No ROA RIR databaseRIPE 673 100% 66
194.226.7.0/24 No ROA RIR databaseRIPE 673 100% 66
46.31.0.0/21 Valid Other origin only 673 100% 67
46.31.0.0/24 Valid Other origin only 673 100% 66
46.31.1.0/24 Valid Other origin only 673 100% 66
46.31.3.0/24 Valid Other origin only 673 100% 66
46.235.54.0/24 Valid Nonecovered by 46.235.54.0/23 673 100% 67
46.235.55.0/24 Valid Nonecovered by 46.235.54.0/23 673 100% 67
91.102.200.0/21 Valid Other origin only 673 100% 66
91.102.200.0/23 Valid Other origin only 673 100% 67
91.102.200.0/24 Valid Other origin only 673 100% 67
91.102.201.0/24 Valid Other origin only 673 100% 66
91.102.202.0/24 Valid Other origin only 673 100% 66
91.102.204.0/24 Valid Other origin only 673 100% 66
91.102.205.0/24 Valid Other origin only 673 100% 67
91.102.206.0/23 Valid Other origin only 673 100% 67
91.102.206.0/24 Valid Other origin only 673 100% 66
91.102.207.0/24 Valid Other origin only 673 100% 66
46.31.6.0/24 Valid Other origin only 672 100% 66
46.31.0.0/23 Valid Other origin only 153 23% 44
46.235.49.0/24 Valid RIR databaseRIPE 673 100% 66
46.235.50.0/24 Valid RIR databaseRIPE 673 100% 66
46.235.51.0/24 Valid RIR databaseRIPE 673 100% 66
195.208.200.0/24 Valid RIR databaseRIPE 673 100% 66
195.208.201.0/24 Valid RIR databaseRIPE 673 100% 66
195.208.202.0/24 Valid RIR databaseRIPE 673 100% 66
195.209.100.0/24 Valid RIR databaseRIPE 673 100% 67
195.209.101.0/24 Valid RIR databaseRIPE 673 100% 66
195.208.203.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS51764 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 27 are in fix.csv.

  • ROA: none2
  • Route object: none18
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none194.226.6.0/24No ROA covers it. Add a ROA for AS51764, maxLength 24.673 of 673
ROA: none194.226.7.0/24No ROA covers it. Add a ROA for AS51764, maxLength 24.673 of 673
Route object: none46.31.0.0/21Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none46.31.0.0/24Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none46.31.1.0/24Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none46.31.3.0/24Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none46.235.54.0/24No route object for it. A route object for 46.235.54.0/23 with origin AS51764 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none46.235.55.0/24No route object for it. A route object for 46.235.54.0/23 with origin AS51764 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none91.102.200.0/21Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none91.102.200.0/23Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none91.102.200.0/24Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none91.102.201.0/24Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none91.102.202.0/24Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none91.102.204.0/24Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none91.102.205.0/24Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none91.102.206.0/23Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none91.102.206.0/24Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none91.102.207.0/24Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.673 of 673
Route object: none46.31.6.0/24Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.672 of 673
Route object: none46.31.0.0/23Route objects for it name AS41942. Add a route object with origin AS51764 in the RIR database for the space.153 of 673

Route objects not announced

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

46.235.48.0/24RIPEValid
46.235.54.0/23RIPENo ROA
194.226.6.0/23RIPENo ROA
195.208.200.0/22RIPENo ROA
195.208.200.0/23RIPENo ROA
195.208.202.0/23RIPENo ROA
195.209.100.0/23RIPENo 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.