bgpreport

Network · data from 2026-11-12

AS206977 azstatenet STATE SERVICE OF SPECIAL COMMUNICATION AND INFORMATION SECURITY OF THE REPUBLIC OF AZERBAIJAN

Registry name: azstatenet STATE SERVICE OF SPECIAL COMMUNICATION AND INFORMATION SECURITY OF THE REPUBLIC OF AZERBAIJAN, AZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206977, 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.
91.103.137.0/24 No ROA RIR databaseRIPE 673 100% 66
178.76.0.0/22 No ROA RIR databaseRIPE 673 100% 66
178.76.4.0/24 No ROA RIR databaseRIPE 673 100% 66
178.76.6.0/24 No ROA RIR databaseRIPE 673 100% 67
178.76.7.0/24 No ROA RIR databaseRIPE 673 100% 67
178.76.5.0/24 No ROA RIR databaseRIPE 672 100% 66
185.93.90.0/24 No ROA RIR databaseRIPE 672 100% 66
31.170.233.0/24 Valid RIR databaseRIPE 673 100% 66
31.170.234.0/24 Valid RIR databaseRIPE 673 100% 66
31.170.235.0/24 Valid RIR databaseRIPE 673 100% 66
31.170.236.0/24 Valid RIR databaseRIPE 673 100% 66
31.170.237.0/24 Valid RIR databaseRIPE 673 100% 66
31.170.238.0/24 Valid RIR databaseRIPE 673 100% 66
31.170.239.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.24.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.26.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.27.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.58.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.65.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.66.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.70.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.121.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.122.0/24 Valid RIR databaseRIPE 673 100% 66
94.20.63.0/24 Valid RIR databaseRIPE 673 100% 66
94.20.157.0/24 Valid RIR databaseRIPE 673 100% 66
31.170.232.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS206977 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 25 are in fix.csv.

  • ROA: none7
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none91.103.137.0/24No ROA covers it. Add a ROA for AS206977, maxLength 24.673 of 673
ROA: none178.76.0.0/22No ROA covers it. Add a ROA for AS206977, maxLength 22.673 of 673
ROA: none178.76.4.0/24No ROA covers it. Add a ROA for AS206977, maxLength 24.673 of 673
ROA: none178.76.6.0/24No ROA covers it. Add a ROA for AS206977, maxLength 24.673 of 673
ROA: none178.76.7.0/24No ROA covers it. Add a ROA for AS206977, maxLength 24.673 of 673
ROA: none178.76.5.0/24No ROA covers it. Add a ROA for AS206977, maxLength 24.672 of 673
ROA: none185.93.90.0/24No ROA covers it. Add a ROA for AS206977, maxLength 24.672 of 673

Route objects not announced

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

31.170.232.0/21RIPENo ROA
31.171.112.0/24RIPEValid
31.171.113.0/24RIPEValid
31.171.114.0/24RIPEValid
31.171.115.0/24RIPEValid
37.61.64.0/24RIPEValid
37.61.65.0/24RIPEValid
37.61.66.0/24RIPEValid
37.61.67.0/24RIPEValid
178.76.0.0/24RIPENo ROA
178.76.1.0/24RIPENo ROA
178.76.2.0/24RIPENo ROA
178.76.3.0/24RIPENo ROA
185.138.12.0/24RIPEValid
185.138.13.0/24RIPEValid
185.138.14.0/24RIPEValid
185.138.15.0/24RIPEValid
188.72.129.0/24RIPENo 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.