bgpreport

Network · data from 2026-11-12

AS8814 AS-AZTELEKOM Aztelekom LLC

Registry name: AS-AZTELEKOM Aztelekom LLC, AZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8814, 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.135.245.0/24 Valid RIR databaseRIPE 672 100% 66
91.135.246.0/24 Valid RIR databaseRIPE 672 100% 66
91.135.247.0/24 Valid RIR databaseRIPE 672 100% 66
91.135.248.0/24 Valid RIR databaseRIPE 672 100% 66
91.135.249.0/24 Valid RIR databaseRIPE 672 100% 66
91.135.250.0/24 Valid RIR databaseRIPE 672 100% 66
91.135.251.0/24 Valid RIR databaseRIPE 672 100% 66
91.135.254.0/24 Valid RIR databaseRIPE 672 100% 66
91.135.255.0/24 Valid RIR databaseRIPE 672 100% 66
92.39.88.0/24 Valid RIR databaseRIPE 672 100% 66
92.39.89.0/24 Valid RIR databaseRIPE 672 100% 66
92.39.95.0/24 Valid RIR databaseRIPE 672 100% 66
158.181.32.0/24 Valid RIR databaseRIPE 672 100% 66
158.181.33.0/24 Valid RIR databaseRIPE 672 100% 66
158.181.35.0/24 Valid RIR databaseRIPE 672 100% 66
158.181.36.0/24 Valid RIR databaseRIPE 672 100% 66
158.181.40.0/22 Valid RIR databaseRIPE 672 100% 66
158.181.44.0/22 Valid RIR databaseRIPE 672 100% 66
185.92.227.0/24 Valid RIR databaseRIPE 672 100% 67
194.135.152.0/24 Valid RIR databaseRIPE 672 100% 66
194.135.153.0/24 Valid RIR databaseRIPE 672 100% 66
194.135.154.0/24 Valid RIR databaseRIPE 672 100% 66
194.135.155.0/24 Valid RIR databaseRIPE 672 100% 66
194.135.156.0/24 Valid RIR databaseRIPE 672 100% 66
194.135.157.0/24 Valid RIR databaseRIPE 672 100% 66
194.135.158.0/24 Valid RIR databaseRIPE 672 100% 66
194.135.159.0/24 Valid RIR databaseRIPE 672 100% 66
194.135.160.0/24 Valid RIR databaseRIPE 672 100% 66
212.47.128.0/22 Valid RIR databaseRIPE 672 100% 66
212.47.132.0/22 Valid RIR databaseRIPE 672 100% 66
212.47.136.0/22 Valid RIR databaseRIPE 672 100% 66
212.47.140.0/22 Valid RIR databaseRIPE 672 100% 66
212.47.144.0/22 Valid RIR databaseRIPE 672 100% 66
212.47.148.0/22 Valid RIR databaseRIPE 672 100% 66
212.47.159.0/24 Valid RIR databaseRIPE 672 100% 66
80.69.52.0/24 Valid RIR databaseRIPE 671 100% 66
80.69.54.0/24 Valid RIR databaseRIPE 671 100% 66
80.69.55.0/24 Valid RIR databaseRIPE 671 100% 66
80.69.58.0/24 Valid RIR databaseRIPE 671 100% 66
80.69.59.0/24 Valid RIR databaseRIPE 671 100% 66
80.69.61.0/24 Valid RIR databaseRIPE 671 100% 66
80.69.62.0/24 Valid RIR databaseRIPE 671 100% 66
80.69.63.0/24 Valid RIR databaseRIPE 671 100% 66

AS-SET

AS8814 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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