hey António,
you are not alone in this. what you are describing sounds like a classic case of regional performance degradation or a 'brownout'. the service is still technically up, but it is running so slowly that it might as well be down. the health status pages are often the last to reflect these issues.
first, let's get some proof. open the azure portal and go to your document intelligence resource. look at the 'monitoring' section and check the 'latency' and 'availability' metrics for the last 48 hours. this data is often more detailed and real time than the public status page. if u see a spike in latency around the times u mentioned, that is your evidence.
also, enable diagnostic settings for your resource if u haven't already. send logs to a log analytics workspace. this will capture detailed request by request data, including failures and slow responses. u can use this data to prove the issue to support.
with this data in hand, u must contact azure support immediately. open a severity a ticket. provide them with your resource id, region, and the exact timestamps of the poor performance. the support engineers have access to backend metrics that we cannot see. they can confirm if there is a platform issue affecting west europe.
for the frequent momentary downtimes, that is a serious concern. it suggests underlying instability in the region. again, support is your best path. they can investigate if your resources are being moved or updated behind the scenes, causing these brief outages.
really hope they resolve this for u quickly. unreliable performance from a core ai service is a major problem.
Best regards,
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer
https://ctrlaltdel.blog/