bgpreport

Network · data from 2026-11-12

AS44285 SEFROYEKPARDAZENG-AS Sefroyek Pardaz Engineering PJSC

Registry name: SEFROYEKPARDAZENG-AS Sefroyek Pardaz Engineering PJSC, IR · not in PeeringDB

42IPv4 routes 95.2% RPKI valid · 92.9% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
0No ROA 3 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
32Route objects not announced registered with origin AS44285, seen from no peer

Announced routes

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

185.182.248.0/23 Invalid: origin RIR databaseRIPE 2 0%low visibility 2
185.182.250.0/23 Invalid: origin RIR databaseRIPE 2 0%low visibility 2
45.87.4.0/23 Valid None 671 100% 66
46.28.78.0/23 Valid Other origin onlycovered by 46.28.72.0/21 671 100% 66
84.47.230.0/23 Valid Nonecovered by 84.47.228.0/22 671 100% 66
85.198.24.0/22 Valid RIR databaseRIPE 672 100% 66
85.198.27.0/24 Valid RIR databaseRIPE 672 100% 66
185.121.130.0/24 Valid RIR databaseRIPE 672 100% 66
5.1.43.0/24 Valid RIR databaseRIPE 671 100% 66
37.32.32.0/22 Valid RIR databaseRIPE 671 100% 66
37.75.243.0/24 Valid RIR databaseRIPE 671 100% 66
37.75.244.0/24 Valid RIR databaseRIPE 671 100% 66
37.75.245.0/24 Valid RIR databaseRIPE 671 100% 66
37.75.246.0/24 Valid RIR databaseRIPE 671 100% 66
37.75.247.0/24 Valid RIR databaseRIPE 671 100% 66
45.140.224.0/22 Valid RIR databaseRIPE 671 100% 66
84.47.224.0/24 Valid RIR databaseRIPE 671 100% 66
84.47.225.0/24 Valid RIR databaseRIPE 671 100% 66
84.47.226.0/24 Valid RIR databaseRIPE 671 100% 66
84.47.227.0/24 Valid RIR databaseRIPE 671 100% 66
84.47.228.0/24 Valid RIR databaseRIPE 671 100% 66
84.47.229.0/24 Valid RIR databaseRIPE 671 100% 66
84.47.230.0/24 Valid RIR databaseRIPE 671 100% 66
84.47.231.0/24 Valid RIR databaseRIPE 671 100% 66
85.198.24.0/24 Valid RIR databaseRIPE 671 100% 66
85.198.25.0/24 Valid RIR databaseRIPE 671 100% 66
85.198.26.0/24 Valid RIR databaseRIPE 671 100% 66
185.121.128.0/24 Valid RIR databaseRIPE 671 100% 66
185.121.129.0/24 Valid RIR databaseRIPE 671 100% 66
185.121.131.0/24 Valid RIR databaseRIPE 671 100% 66
185.171.54.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
185.171.55.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
217.172.120.0/21 Valid RIR databaseRIPE 671 100% 66
45.9.252.0/24 Valid RIR databaseRIPE 670 100% 66
45.9.253.0/24 Valid RIR databaseRIPE 670 100% 66
45.9.254.0/24 Valid RIR databaseRIPE 670 100% 66
46.28.72.0/24 Valid RIR databaseRIPE 670 100% 66
46.28.73.0/24 Valid RIR databaseRIPE 670 100% 66
46.28.74.0/24 Valid RIR databaseRIPE 670 100% 66
46.28.75.0/24 Valid RIR databaseRIPE 670 100% 66
46.28.76.0/24 Valid RIR databaseRIPE 670 100% 66
46.28.77.0/24 Valid RIR databaseRIPE 670 100% 66
2a02:828::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS44285 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 37 are in fix.csv.

  • ROA: origin2
  • Route object: none3
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: origin185.182.248.0/23ROAs covering it name AS48715, not AS44285. If AS44285 should announce it, add a ROA for AS44285.2 of 673
ROA: origin185.182.250.0/23ROAs covering it name AS48715, not AS44285. If AS44285 should announce it, add a ROA for AS44285.2 of 673
Route object: none45.87.4.0/23No route object for it. Add a route object with origin AS44285 in the RIR database for the space.671 of 673
Route object: none46.28.78.0/23Route objects for it name AS58053. A route object for 46.28.72.0/21 with origin AS44285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44285 in the RIR database for the space.671 of 673
Route object: none84.47.230.0/23No route object for it. A route object for 84.47.228.0/22 with origin AS44285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44285 in the RIR database for the space.671 of 673

Route objects not announced

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

37.32.32.0/21RIPENo ROA
37.75.244.0/22RIPEValid
45.9.252.0/22RIPEValid
45.9.252.0/23RIPEValid
45.9.254.0/23RIPEValid
45.156.180.0/22RIPEValid
46.28.72.0/21RIPEValid
80.249.114.0/24RIPEValid
84.47.224.0/21RIPEValid
84.47.224.0/22RADB, RIPEValid
84.47.228.0/22RIPEValid
185.121.128.0/22RIPEValid
185.121.130.0/23RIPEValid
185.182.250.0/24RIPEInvalid: origin
185.182.251.0/24RIPEInvalid: origin
188.209.152.0/23RIPEValid
195.110.38.0/24RIPEValid
195.110.39.0/24RIPEValid
217.172.120.0/24RIPEValid
217.172.124.0/23RIPEValid
217.172.126.0/23RIPEValid
2a02:828::/29RIPEValid
2a02:828::/32RIPEValid
2a02:828::/64RIPEValid
2a02:828:1::/48RIPEValid
2a02:829::/32RIPEValid
2a02:82a::/32RIPEValid
2a02:82b::/32RIPEValid
2a02:82c::/32RIPEValid
2a02:82d::/32RIPEValid
2a02:82e::/32RIPEValid
2a02:82f::/32RIPEValid

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.