bgpreport

Network · data from 2026-11-12

AS44725 AZQTEL-AS Sinam LLC

Registry name: AZQTEL-AS Sinam LLC, AZ · not in PeeringDB

4IPv4 routes 50.0% RPKI valid · 75.0% with a route object
0IPv6 routes
1RPKI invalid 0 origin · 1 maxLength
1No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS44725, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS44725, 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.
5.250.208.0/20 Invalid: maxLength RIR databaseRIPE 1 0%low visibility 1
92.39.80.0/21 No ROA RIR databaseRIPE 673 100% 67
37.114.128.0/24 Valid None 672 100% 66
5.250.192.0/19 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS44725 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 11 are in fix.csv.

  • ROA: maxLength1
  • ROA: none1
  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: maxLength5.250.208.0/20ROA 5.250.192.0/19 AS44725 has maxLength 19; the route is a /20. Raise the maxLength, or add a ROA for 5.250.208.0/20.1 of 673
ROA: none92.39.80.0/21No ROA covers it. Add a ROA for AS44725, maxLength 21.673 of 673
Route object: none37.114.128.0/24No route object for it. Add a route object with origin AS44725 in the RIR database for the space.672 of 673

Route objects not announced

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

92.39.80.0/24RIPENo ROA
92.39.81.0/24RIPENo ROA
92.39.82.0/24RIPENo ROA
92.39.83.0/24RIPENo ROA
92.39.84.0/24RIPENo ROA
92.39.85.0/24RIPENo ROA
92.39.86.0/24RIPENo ROA
92.39.87.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.