I'm not sure that all country (EU), but the most part I'm sure have the same situation but on wide-network project (national network o corporate network projects). Evaluating team members and project managers, you'll not see a lot of professional needed. Not only architect but also other profiles.

The same "worst" practice are used: the general manager of an IT company consider an architect needed only when are developing "THE software" or "THE network infrastructure".
Sometimes only if the software is the next software (not next release) of the company.

But if you are developing software for customers usually the presence of an architect is only a "cost". Usually the IT manager of the customers think the same: "our project is not so important to need an architect. I know all details and all our architectures".

Another case is with company that resell develop software: will happen that architect are unneeded. Having specific competence on the subjetcs how can you resell officially an architect to a customer when the company present itself like the best in competence on his "sector/market".

In the last years, during my PM role, only 2 nationl project about 10 project have all role needed....

The software will be less expensive, more "reusable" and more efficient when every development team have an Architect.
The developer write poor software without an architect (or a mentor). The same is for projects about networking, security and so on.

To have architects in every development team I suppose we need an evolution: In the future the "cut-cost" will increase ever and ever. At that point the price x project will be measured with specific service level agreement (performance, transaction and so on). No more with developer times, competence and team members.

This will be a new starting point for developing company.
At this point only the company that use all needed professionals (architect, operation, etc etc) will raise again....